fix: initialise nextjs webpack before importing devserver #15881
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.
User facing changelog
Fixed integration with nextjs for component test runner
Additional details
NextJs provides its own webpack bundle, rather than listing it as a [peer] dependency. This leads to two separate instances, and potentially two separate versions, of webpack being in use simultaneously.
The NextJs config adds a require hook such that
require('webpack')
returns the bundled NextJs version appropriate to the{future:webpack5}
setting inconfig.next.js
- but as the@cypress/webpack-devserver
package requires webpack, this only works if that package isrequire
d after the next config file has runHow has the user experience changed?
cypress open-ct
now progresses to show test runner when next config is used as per the example in the repositoryPR Tasks