VS Code problemMatcher-friendly reporter about knip HOT 4 OPEN

Did you try creating a custom reporter that is vscode problemMatchers friendly ?

That's what this issue is proposing :) I haven't taken a crack at it myself yet.

from knip.

The output format of knip isn't the best for parsing.

Did you see the JSON reporter? https://knip.dev/features/reporters#json

This works pretty well:

Nice! Great to see Knip used like this.

there aren't line numbers for the unused devDependencies

That's a good RFC.

So call this a feature request for a new reporter that's compatible with one of VS Code's built-in problem matchers, for example "tsc" or "eslint".

What would be the best way to go about this? Use the JSON reporter as a basis, or implement a new reporter for VS Code? Either way, I'll try to read up on the topic a bit more when I can, I'm not familiar with this part of VS Code at all.

Anybody reading this, definitely feel free to pick this up, might be a fun task.

from knip.

The output format of knip isn't the best for parsing.

Did you see the JSON reporter? https://knip.dev/features/reporters#json

Yes! You'd think JSON output would be perfect for consuming from another tool, but so far as I can tell VS Code problemMatchers really want line-based output.

This works pretty well:

Nice! Great to see Knip used like this.

there aren't line numbers for the unused devDependencies

That's a good RFC.

Want me to file an issue for this?

So call this a feature request for a new reporter that's compatible with one of VS Code's built-in problem matchers, for example "tsc" or "eslint".

What would be the best way to go about this? Use the JSON reporter as a basis, or implement a new reporter for VS Code? Either way, I'll try to read up on the topic a bit more when I can, I'm not familiar with this part of VS Code at all.

Anybody reading this, definitely feel free to pick this up, might be a fun task.

I'd suggest implementing a new reporter that outputs in the exact same format as eslint, tsc or some other tool that VS Code has a built-in matcher for.

from knip.

Yes! You'd think JSON output would be perfect for consuming from another tool, but so far as I can tell VS Code problemMatchers really want line-based output.

Did you try creating a custom reporter that is vscode problemMatchers friendly ?

from knip.