Lars Kappert

Closing due to inactivity.

@yishuolin Thanks, so you're having the same issue? That could very well be the cause indeed. Would you like submit a pull request? No worries if not and I'll investigate/pick...

@yishuolin @kirkbaly I might have a fix, would be great if you could test this version in your project(s): ``` npm i -D https://pkg.pr.new/knip@249794a ```

Thank you so much for confirming. I'll release it today.

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

Maybe what we could consider and investigate is remove more dependencies from `code/package.json` to make packages more self-contained. Then Knip can detect them properly as well. pnpm would help here...

lol yes I forgot about [strict mode](https://knip.dev/features/production-mode#strict-mode), and didn't use that in my latest PR here unfortunately. Comes with more strictness, isolated packages should probably be separate flag. So many...

> I think for consistency between screens I'd keep the badge. Sure, it's a bit redundant here, but dropping the badge introduces a difference in behavior that imo contributes to...

Knip supports JSX/TSX files, but the [default Nuxt configuration](https://knip.dev/reference/plugins/nuxt#default-configuration) only has `app.vue` included, not `app.tsx`. That's why `app.tsx` isn't included in the analysis by default. You could add this to...

Looks like `app.tsx` isn't a default file picked up by Nuxt? Looking at https://nuxt.com/docs/guide/directory-structure/app Btw, you could also leave the Nuxt defaults as they are, and add a generic `entry`...