-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Open
Labels
CTIssue related to component testingIssue related to component testingtype: featureNew feature that does not currently existNew feature that does not currently exist
Description
What would you like?
Support Next.js 16 for Component Testing
See also Migration Guide Next.js 15 to 16
Why is this needed?
Next.js 16 was announced on Oct 21, 2025.
Cypress currently supports Next.js 14-15 as documented on https://docs.cypress.io/app/component-testing/get-started#Supported-Frameworks and
cypress/packages/scaffold-config/src/dependencies.ts
Lines 55 to 65 in 34fe1ae
| export const WIZARD_DEPENDENCY_NEXT = { | |
| type: 'next', | |
| name: 'Next', | |
| package: 'next', | |
| installer: 'next', | |
| description: 'The React Framework for Production', | |
| // next 15.0.0 -> 15.0.3 use the React 19 RC as a dependency | |
| // Since we do not support the React 19 RC and only the official React 19 release, | |
| // we will only be supporting Next.js 15.0.4 officially (the others previously mentioned should still work) | |
| minVersion: '^14.0.0 || ^15.0.4', | |
| } as const |
Other
- Users report that it does not work out-of-the-box. See TypeError when running component tests with Next.js 16 and Webpack #32839. This issue could be considered as a duplicate, however the one here is formulated as a feature / enhancement request, rather than a bug report.
chinmaykunkikar, zmays, baniplus, michael-mezgo, SteffenAuer and 3 more
Metadata
Metadata
Assignees
Labels
CTIssue related to component testingIssue related to component testingtype: featureNew feature that does not currently existNew feature that does not currently exist