You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice to have more detail on how to find "where" is defined this configuration:
For example, the vscode console allow us to click on lines "that looks like a filename with a line number" (ie. package.json:15)
Furthermore, some tools like reviewdog does parse the output to report checks on github, but actually it's really complicated to target a file.
Making reviewdog work with depcheck would be really usefull as they are complementary when working with a CI.
I think that it's not as easy as said regarding the JSON output, if that's the data structure that you use internally, as we have an array of string here.
The options I see here:
Do not touch the JSON output, just "improve" the standard output
Add the package line in the array of string ("devDependencies": ["prettier (package.json:15)"]), not pretty, but non-breaking
change the data format : "devDependencies": [ { package: "prettier", "dependencyFile": "package.json", "dependencyLine": 15 } ]
I do not know if the json output is for debbuging purpose or if it is part of public API.
Any extra info
I can give a hand on this if you are OK with this feature.
The text was updated successfully, but these errors were encountered:
Feature request description
Actually, the reported output is something like
In the JSON output, we have
It would be nice to have more detail on how to find "where" is defined this configuration:
For example, the vscode console allow us to click on lines "that looks like a filename with a line number" (ie.
package.json:15
)Furthermore, some tools like reviewdog does parse the output to report checks on github, but actually it's really complicated to target a file.
Making reviewdog work with depcheck would be really usefull as they are complementary when working with a CI.
A possible nice output would be
I think that it's not as easy as said regarding the JSON output, if that's the data structure that you use internally, as we have an array of string here.
The options I see here:
"devDependencies": ["prettier (package.json:15)"]
), not pretty, but non-breaking"devDependencies": [ { package: "prettier", "dependencyFile": "package.json", "dependencyLine": 15 } ]
I do not know if the json output is for debbuging purpose or if it is part of public API.
Any extra info
I can give a hand on this if you are OK with this feature.
The text was updated successfully, but these errors were encountered: