-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Support {m,c}{j,t}s file extensions for tests and modules #14149
Comments
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days. |
This is still an issue. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days. |
This is still an issue. |
I think it would be fine to add Not sure about |
Can I try to fix it? |
Sure. As I mentioned, these are breaking changes, so PRs can only land with the next major release. It is fine to open them now, of course. |
Probably, this issue needs to be open.
|
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Version
29.5.0
Steps to reproduce
npm install-test
Expected behavior
Jest runs all tests.
Actual behavior
Jest only runs tests with extensions:
Jest doesn't run tests with extensions:
Additional context
testMatch
andtestRegex
.mts
andmts
are missing frommoduleFileExtensions
.Environment
System: OS: macOS 12.6.5 CPU: (4) x64 Intel(R) Core(TM) i5-5257U CPU @ 2.70GHz Binaries: Node: 20.1.0 - /usr/local/bin/node Yarn: 1.22.19 - /usr/local/bin/yarn npm: 9.6.6 - /usr/local/bin/npm npmPackages: jest: 29.5.0 => 29.5.0
The text was updated successfully, but these errors were encountered: