Next.js ^11.1.1 : webpack error + bundling step timeout
See original GitHub issueCurrent behavior
Using the create next app webpack 5 example setup, with "next": "latest"
that resolves to ^11.1.1
.
Result in a TypeError and a timeout on the bundling step
✖ 「wdm」: TypeError: Cannot read property 'traceChild' of undefined
...
ℹ 「wdm」: wait until bundle finished: /__cypress/src/index.html
Desired behavior
No response
Test code to reproduce
create next app webpack 5 example setup with "next": "latest"
(11.1.1
or 11.1.2
)
Cypress Version
^8.3.0
Other
workaround / temporary solution :
use exact version at 11.1.0
"next": "11.1.0"
tnx https://github.com/cypress-io/cypress/discussions/17883#discussioncomment-1233406
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (6 by maintainers)
Top Results From Across the Web
Node.js v17.0.0 - Error starting project in development mode ...
js to the new version, when starting the project in development mode, the following error is obtained in the terminal. > test@0.1.0 dev...
Read more >Blog - Next.js 11.1
Next.js 11.1 introduces an important security patch, ES Modules support, performance improvements, Rust-based tooling, 2x faster data ...
Read more >page-data-collection-timeout - Next.js
Next.js tries to restart the worker pool of the page data collection when no progress happens for a while, to avoid hanging builds....
Read more >static-page-generation-timeout - Next.js
When restarted it will retry all uncompleted jobs, but if a job was unsuccessfully attempted multiple times, this will lead to an error....
Read more >Upgrade Guide - Next.js
This new parser has improved handling of CSS and now errors when invalid CSS is used ... As communicated in the webpack 5...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I was able to reproduce this issue @g10. After some digging, I found that Next added tracing (collecting performance metrics) to many of it’s internal Webpack plugins in 11.1.1. This is a breaking change since for us since we use their default webpack config and don’t specify a trace. The fix should be pretty straight-forward but Next currently doesn’t export any of the tracing code so I’ll followup with the Next team to see if they can export what we need.
Edit: Nvm I found the deep export I was looking for. I have a PR to fix this here https://github.com/cypress-io/cypress/pull/18189
FYI: I just found a root cause and made a PR https://github.com/cypress-io/cypress/pull/18648