fix(testing): add NODE_OPTIONS flag for Node.js 24 compatibility #32177
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Jest 30 + Node.js 24 can't parse TS configs with imports without the --no-experimental-strip-types flag. This change automatically adds the flag when running Jest tests on Node.js 24+. Fixes the issue where Jest fails to parse TypeScript config files with ES module syntax on Node.js 24. Related to: jestjs/jest#15682
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Contributor
|
View your CI Pipeline Execution ↗ for commit 0d76f70
☁️ Nx Cloud last updated this comment at |
jaysoo
approved these changes
Jul 31, 2025
jaysoo
pushed a commit
that referenced
this pull request
Aug 1, 2025
) ## Current Behavior Jest fails to parse TypeScript config files with ES module syntax on Node.js 24 with error: ``` Error: Jest: Failed to parse the TypeScript config file SyntaxError: Unexpected token 'export' ``` ## Expected Behavior Jest should successfully parse TypeScript config files on Node.js 24. ## Related Issue(s) This occurs because Jest 30 + Node.js 24 can't parse TS configs with imports without the `--no-experimental-strip-types` flag. Related to: jestjs/jest#15682
ndcunningham
added a commit
that referenced
this pull request
Aug 1, 2025
) ## Current Behavior Jest fails to parse TypeScript config files with ES module syntax on Node.js 24 with error: ``` Error: Jest: Failed to parse the TypeScript config file SyntaxError: Unexpected token 'export' ``` ## Expected Behavior Jest should successfully parse TypeScript config files on Node.js 24. ## Related Issue(s) This occurs because Jest 30 + Node.js 24 can't parse TS configs with imports without the `--no-experimental-strip-types` flag. Related to: jestjs/jest#15682
Contributor
|
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Current Behavior
Jest fails to parse TypeScript config files with ES module syntax on Node.js 24 with error:
Expected Behavior
Jest should successfully parse TypeScript config files on Node.js 24.
Related Issue(s)
This occurs because Jest 30 + Node.js 24 can't parse TS configs with imports without the
--no-experimental-strip-typesflag.Related to: jestjs/jest#15682