fix(nextjs): use next/jest.js for Jest configuration to support modern JSX transform #31705
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.
This PR fixes and issue with Next.js + Jest to remove warnings about outdated transforms.
Changes Made
Current Behavior
When using React 19 with Next.js applications in Nx, developers receive a warning about outdated JSX transform because the Jest configuration uses
manual babel-jest setup instead of Next.js's recommended approach.
Expected Behavior
Next.js applications and libraries generated by Nx should use next/jest.js configuration which automatically handles the modern JSX transform
(runtime: 'automatic') and provides proper Jest setup for Next.js projects without warnings.
Related Issue(s)
Fixes #27900