-
Notifications
You must be signed in to change notification settings - Fork 26.8k
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 from 10.0.0 to 10.0.5 failed with "webpack config.resolve.alias was incorrectly overridden" #20950
Comments
Digging deeper and focusing on the issue at hand, I could figure out this is the behaviour since Next.js v10.0.4. See UnlyEd/next-right-now#243 I ran the same code under 5 version (10.0.0 ... 10.0.5) of Next, and the 10.0.4 and 10.0.5 failed with the same error output. |
The issue here is that you're using incorrect configuration values, only |
@timneutkens I think it's only part of the overall problem.
I'll change the poweredByHeader, but the other error doesn't seem related to |
You were right, the |
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. |
What version of Next.js are you using?
10.0.5
What version of Node.js are you using?
12
What browser are you using?
Chrome
What operating system are you using?
MacOS
How are you deploying your application?
Vercel
Describe the Bug
20:41:30.594 Module parse failed: Unexpected token (52:30)
20:41:30.594 File was processed with these loaders:
20:41:30.594 * ./node_modules/next/dist/build/webpack/loaders/next-serverless-loader/index.js
20:41:30.594 You may need an additional loader to handle the result of these loaders.
20:41:30.594 | canonicalBase: "",
20:41:30.594 | generateEtags: true,
20:41:30.594 > poweredByHeader: Next Right Now - With love - https://github.com/UnlyEd/next-right-now,
20:41:30.594 |
20:41:30.594 | runtimeConfig,
20:41:30.594 > Build error occurred
20:41:30.595 Error: > webpack config.resolve.alias was incorrectly overridden. https://err.sh/vercel/next.js/invalid-resolve-alias
20:41:30.595 at /vercel/workpath0/node_modules/next/dist/build/index.js:15:787
20:41:30.595 at async /vercel/workpath0/node_modules/next/dist/build/tracer.js:1:525
20:41:30.659 error Command failed with exit code 1.
Expected Behavior
Should build, was building fine before migrating to Next.js v10.0.5, from v10.0.0
To Reproduce
Deploy UnlyEd/next-right-now#243 on Vercel
Vercel deploy logs:
Here is the content of my
next.config.js
file:It seems the issue might be related to
config.resolve.alias['@sentry/node'] = '@sentry/browser';
(from the error message). This used to work fine since Next.js v9. Did something change?I don't know if that's related to Vercel or Next. Most likely Next.js itself.
Also, there seems to be an issue with the
poweredByHeader
, once again, this used to work fine.The text was updated successfully, but these errors were encountered: