Skip to content
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

Upgrade to webpack-sources 3.2.1 #30920

Closed
wuzzeb opened this issue Nov 3, 2021 · 1 comment · Fixed by #30944
Closed

Upgrade to webpack-sources 3.2.1 #30920

wuzzeb opened this issue Nov 3, 2021 · 1 comment · Fixed by #30944
Labels
bug Issue was opened via the bug report template.

Comments

@wuzzeb
Copy link

wuzzeb commented Nov 3, 2021

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#L266

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

@wuzzeb wuzzeb added the bug Issue was opened via the bug report template. label Nov 3, 2021
@kodiakhq kodiakhq bot closed this as completed in #30944 Nov 4, 2021
kodiakhq bot pushed a commit that referenced this issue Nov 4, 2021
@balazsorban44
Copy link
Member

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 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
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue was opened via the bug report template.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants