🔄 Jest configured setup scripts reporting as unused exports when --include-entry-exports is enabled

[stfstoris]

Prerequisites

• I've read the relevant documentation
• I've searched for existing issues
• I've read the issue reproduction guide

Reproduction url

https://github.com/stfstoris/knip-jest-setup-issue

Reproduction access

• I've made sure the reproduction is publicly accessible

Good version

5.33.3

Bad version

5.34.0

Description of the regression

Reproduction of issue: https://github.com/stfstoris/knip-jest-setup-issue

There seems to be a regression of an issue my colleague @shawnmcknight logged a while back: #716, where after we updated knip to latest we are now getting unused export errors from our jest setup and teardown files with --include-entry-exports enabled:

Running this on any version after original fix version (5.24.2) and before version 5.34.0 does not give us this error, so it appears that this version introduced regression:

[webpro]

Thanks the report, @stfstoris! Did a major refactoring around that version and I've missed something indeed. Should be sorted in the next.

[webpro]

🚀 This issue has been resolved in v5.38.1. See Release 5.38.1 for release notes.

Using Knip in a commercial project? Please consider becoming a sponsor.

[stfstoris]

@webpro thank you for the quick fix!

[webpro]

🫡