Lars Kappert

:rocket: _This issue has been resolved in v5.14.0. See [Release 5.14.0](https://github.com/webpro/knip/releases/tag/5.14.0) for release notes._ _Using Knip in a commercial project? Please consider [sponsoring me](https://github.com/sponsors/webpro)._

Knip should definitely not choke on those indeed. A PR would be great, otherwise I'll pick it up after the weekend.

:rocket: _This issue has been resolved in v5.17.4. See [Release 5.17.4](https://github.com/webpro-nl/knip/releases/tag/5.17.4) for release notes._ _Using Knip in a commercial project? Please consider [sponsoring me](https://github.com/sponsors/webpro)._

Yes, that's interesting :) You can already use custom reporters, but would be great to include them with Knip for others to enjoy as well.

This issue is specific to monorepos. Knip should not match `start:server` in the current workspace, but in `-F this` one. Unfortunately this isn't trivial given how Knip currently handles this....

Closing this as "wontfix".

Thanks for the report, @mountEvarus. This is the Jest plugin: https://github.com/webpro/knip/blob/main/packages/knip/src/plugins/jest/index.ts Any chance you're up for a PR? No worries if not!

They're supported. But there could be a bug. What's the issue you're seeing? A common pitfall is that the `main` or subpath `imports` point to ignored/dist files, which aren't added...

I remember `#*` and `#/*` aren't valid aliases. Maybe TypeScript accepts them, but the Node.js runtime does not. Can you try valid aliases and see if that works better? Also...

> Are you sure it isn't just `#/*` that's invalid? No, I haven't actually used this alias myself. Could you please provide a reproduction of the issue, so I can...