You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
webpack-sources v3.2.0 had a bug that in some cases it can cause a stack overflow. It was documented in webpack/webpack-sources#131 and the problem was fixed in the v3.2.1 release of webpack-sources.
Also, next.js is using the bundled webpack-sources from node_modules/next/dist/compiled/webpack-sources directory.
Is there any way to override that and use a webpack-sources specified in the resolutions section of package.json so I can use v3.2.1 which contains the fix?
Expected Behavior
next build runs without producing a stack overflow.
To Reproduce
Not really needed since the bug has already been fixed. Just need next.js to update to webpack-sources v3.2.1
The text was updated successfully, but these errors were encountered:
This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.
vercel
locked as resolved and limited conversation to collaborators
Jan 27, 2022
natew
pushed a commit
to natew/next.js
that referenced
this issue
Feb 16, 2022
What version of Next.js are you using?
12.0.2
What version of Node.js are you using?
16.11.1
What browser are you using?
Firefox
What operating system are you using?
Linux
How are you deploying your application?
next export
Describe the Bug
webpack-sources v3.2.0 had a bug that in some cases it can cause a stack overflow. It was documented in webpack/webpack-sources#131 and the problem was fixed in the v3.2.1 release of webpack-sources.
I'm hitting the same issue when running
next build
(a maximum call stack size exceeded) because at the moment next is pinned to v3.2.0 see https://github.com/vercel/next.js/blob/canary/packages/next/package.json#L266Also, next.js is using the bundled webpack-sources from
node_modules/next/dist/compiled/webpack-sources
directory.Is there any way to override that and use a
webpack-sources
specified in theresolutions
section of package.json so I can use v3.2.1 which contains the fix?Expected Behavior
next build runs without producing a stack overflow.
To Reproduce
Not really needed since the bug has already been fixed. Just need next.js to update to webpack-sources v3.2.1
The text was updated successfully, but these errors were encountered: