-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Next.js ^11.1.1 : webpack error + bundling step timeout #17992
Comments
Same error in Next version 11.1.2 |
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 #18189 |
The code for this is done in cypress-io/cypress#18189, but has yet to be released. |
Hello, sorry for bumping this up but I see that the fix for this was first merged and then got reverted. Is there any ETA for it? |
@pbilyk Sorry for the confusion. I believe there was a merge that reverted and re-added this commit. Latest master contains the changes so using the latest version of |
Thanks! Seems to work with next 11. But they had to go and release next 12, where it stopped working again 😅 |
Of course it did 😭. Feel free to create an issue about Next 12 not working! |
FYI: I just found a root cause and made a PR #18648 |
Current 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
Desired behavior
No response
Test code to reproduce
create next app webpack 5 example setup with
"next": "latest"
(11.1.1
or11.1.2
)Cypress Version
^8.3.0
Other
workaround / temporary solution :
use exact version at
11.1.0
tnx #17883 (comment)
The text was updated successfully, but these errors were encountered: