Lars Kappert

Related: https://github.com/webpro-nl/knip/issues/678 (would be great if an alternative contains the fix)

Thanks @SuperchupuDev! Now I'd be even happier to start using tinyglobby. Even though the `globStream` feature is currently used only once in this codebase, I do like to have it...

Closing this issue as part of a general cleanup to keep this project sustainable and optimize my time working on it. If you think this is inappropriate or if there...

Perhaps you could shed some light on a few things: - Any projects out there already using Knip in an Electron project? E.g. if it's just missing entry points and/or...

Closing this one due to lack of details. Pull requests for new plugins are welcome.

Valid RFC. Would likely becomes regexes for `ignoreExports` or `ignoreExportTypes` (like `ignoreBinaries` etc already do). For now, you could add a simple [preprocessor](https://knip.dev/features/reporters#preprocessors) function to strip out anything unwanted.

I think it's a bug and we should apply the fixes only on the issues returned from the preprocessor(s). Different issue than OP, though.

Closing this issue as part of a general cleanup to keep this project sustainable and optimize my time working on it. If you think this is inappropriate or if there...

This is basically a dup of https://github.com/webpro-nl/knip/issues/733 Knip only extracts import statements in the built-in "compilers", you'd need to install an actual compiler. And I need to document this properly...

What does the compiled JS look like? The return value is what we're interested in, because that's what Knip is working with.