💡 Preprocessor for VSCode Knip

[jerone]

Suggest an idea for Knip

The VSCode Knip extension is reporting issues that I've excluded via a preprocessor.
So running knip --preprocessor ./knip-processor.ts results in no issue, but the VSCode extension does.

Would it be possible to have the preprocessor be part of the config (preferably).
Or have a new option in VSCode extension settings that allows me to set a preprocessor path for my workspace.

Thanks!

[webpro]

Good idea, I'd consider adding that to the config. Feel free to open a PR if you want.

[morgan-coded]

I'll pick this up if the boundary's right. --preprocessor is CLI-only today, so config-sourced preprocessors seem to need one shared result-transformation stage that the CLI and the language server both run, rather than an editor-only path. Before I build, is that the right boundary? The open contract points I see are CLI-versus-config precedence, the module-resolution base for a config-specified preprocessor, repeated entries, refresh behavior, and loader errors. I would cover the JavaScript, TypeScript, package, and scoped-package loaders plus initial diagnostics, refresh, and CLI/editor parity. A VS Code-only setting and any broader reporter refactor stay out of this pass.

[webpro]

That sounds about right indeed; thank you in advance.