fix: call installBindings for Next.js 16.0.3+ compatibility #33072
+1,028
−10,753
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
Fixes cypress-io#32968 Starting with Next.js 16.0.3, the Turbopack bundler requires tools to proactively call installBindings() to ensure SWC bindings are loaded before webpack loaders attempt to use them. This change adds a call to installBindings() in the Next.js handler before loading the webpack configuration. The call is wrapped in a try-catch to maintain backward compatibility with Next.js versions prior to 16.0.3 where this API does not exist. Changes: - Add installBindings() call in getNextJsPackages() - Make getNextJsPackages() async to properly await installBindings() - Add test coverage for the installBindings logic - Add debug logging for troubleshooting See: vercel/next.js#85787
|
|
Collaborator
|
Contributor
|
@FelixK-Witt thank you for opening a PR to fix this! Changes look good to me, but we need a way to test them in CI/CD. Since there really isn't a great way to unit test this currently, I am going to update the |
… JS coverage on next 16.0.3
AtofStryker
approved these changes
Dec 5, 2025
Contributor
AtofStryker
left a comment
AtofStryker
left a comment
There was a problem hiding this comment.
The source changes look good to me. @jennifer-shehane i updated nextjs-configured and nextjs-unconfigured to next 16 to get test coverage here. Are you able to review those changes as well as the change entry?
jennifer-shehane
approved these changes
Dec 5, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
Close #32968
User facing changelog
Fixes Next.js 16.0.3+ component testing compatibility by proactively calling the
installBindings()API.Additional details
Starting with Next.js 16.0.3, the Turbopack bundler requires tools to proactively call
installBindings()to ensure SWC bindings are loaded before webpack loaders (likenext-swc-loader) attempt to use them. Without this call, users encounter the error:Error: bindings not loaded yet. Either callloadBindingsto wait for them to be available or ensure thatinstallBindingshas already been called..This PR adds the required
installBindings()call in the Next.js webpack dev server handler, wrapped in a try-catch block to maintain backward compatibility with Next.js versions prior to 16.0.3 where this API doesn't exist.Steps to test
next.config.jsexists (notnext.config.ts)cypress open --componentAlso here's an example repo with the patch applied: https://github.com/FelixK-Witt/cypress-next-16-component-testing
How has the user experience changed?
Users on Next.js 16.0.3+ can now successfully run component tests without encountering SWC binding errors.
See: vercel/next.js#85787