fix: add jsx extensions for next default file convention

[Jaxenormus]

This is currently flagged as a false positive since any default.tsx or default.jsx file is not included in the entry point of the project but are also not imported since this is a special next.js file which marks it as unused by knip.

[webpro]

Thanks for the PR! I'll look into it tomorrow, but iirc there was a similar discussion recently where the file turned out to be used by some plugin (not necessarily next/Next.js itself). Any chance you could confirm and/or point me to docs that do?

[Jaxenormus]

Thanks for the PR! I'll look into it tomorrow, but iirc there was a similar discussion recently where the file turned out to be used by some plugin (not necessarily next/Next.js itself). Any chance you could confirm and/or point me to docs that do?

I assume your referring to this discussion only one i could find that was related to this on the repo, next.js doesn't explicitly state in the docs that the extension could also be jsx or tsx but in one of their usage examples for modals they have you write a default.tsx file and in our case this is exactly what we are doing and running into the false positive

[webpro]

Thanks again for the PR and all the details, let's merge this.

[webpro]

🚀 This pull request is included in v5.7.1. See Release 5.7.1 for release notes.

[VladSez]

Sorry, not sure 100% if this is related but after updating to [email protected] next route handler is flagged now as unused export.
I am using knip --include-entry-exports

On [email protected] this is not reported and works as expected

[webpro]

How about v5.7.3? 😜

[VladSez]

It works! Thank you :)