Lars Kappert

This is an interesting case, could be a challenge to resolve it. Assuming the intention of `allFixtures.order1` is `allFixtures.orderFixtures.order1`. And I'm afraid this is a "bridge too far" currently for...

Couldn't resist and went ahead on this myself. This use case should be fixed in [v5.14.0](https://github.com/webpro/knip/releases/tag/5.14.0) and should properly handle exports individually (before, it assumed all members of the namespace...

From TS compiler internals Discord: > I've just come across a case where I think `findReferences` might have a bug: > > - ✅ https://codesandbox.io/p/devbox/github/webpro/knip/main/packages/knip/fixtures/re-exports-aliased-ns?file=%2F1-first.ts%3A1%2C16 - find references of `first`...

Thanks for the demo repo! This is super helpful. Let's break it down a little bit. 1. First case: ```ts import * as orderFixtures from './orderFixtures' export const allFixtures =...

Closing this with [v5.17.0](https://github.com/webpro-nl/knip/releases/tag/5.17.0), feel free to discuss further or open a new issue.

Sorry, currently not having the bandwidth to increase the API surface area of Knip. Same for programmatical usage of Knip itself. It would mean I'd have to support more things,...

Yeah it's fragile.. on most pages it works, though :)

Since previous versions of Knip aren't used that much anymore I'm going to close this. The docs for v3 and v4 are still accessible here: - v3: https://github.com/webpro-nl/knip/tree/v3/packages/docs/src/content/docs - v4:...

> Thank you for your review. Sorry, I thought the default code generated from CLI could be left alone. No worries! Thanks for contributing to Knip, I really appreciate it....

> > No, but specifiers starting with `virtual:` are ignored by default. Sorry, I was wrong about this, they're not ignored. Here's what happened: https://github.com/webpro/knip/issues/370 > And we need to...