Replies: 2 comments 3 replies
-
That sounds like an interesting idea 👍 Other output parsers could be added in the future. |
Beta Was this translation helpful? Give feedback.
-
I've just started using this package to help rewrite a legacy project and clean up tech debt, starting with removing unused dependencies. My plan is to build a command that will run this package (along with others) on a weekly basis and act as a health check, sending a report via email or integrated into an IDP. To achieve this, I'd like to receive the output in JSON format. @icanhazstring I searched the issues for this and noticed that you authored PR #279 to add the output format option. Could this code be extended to produce JSON output? I'm happy to contribute where I can, but I'm quite junior so would really appreciate your thoughts on this. |
Beta Was this translation helpful? Give feedback.
-
As much as I like this tool, simple plain text output does not always cut it.
My task is to extract just the unused packages to add them to a problem report, for humans to read. But I might also be tempted to experimentally remove unused packages and see if this breaks anything (like counter-verify by using composer-require-checker or running tests that used to be green).
The current plain text output is rather hard to parse with shell tools, so I'd like to see some alternative output options:
Comparing this to composer, when I run
composer show
, I can select to only see--outdated
or--direct
dependencies.Beta Was this translation helpful? Give feedback.
All reactions