-
Notifications
You must be signed in to change notification settings - Fork 26.1k
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
Module not found: Can't resolve 'regenerator-runtime' -- after upgrading from 11 to 12.0.2-canary.8 #30605
Comments
Regenerator-runtime is installed, but I'm assuming it's related to the path not being absolute, definitely sounds like a bug, thanks for reporting! https://github.com/vercel/next.js/blob/canary/packages/next/package.json#L106 |
@kdy1 is going to add an option which will allow us to provide the path in next-swc-loader 👍 |
@timneutkens Any updates on this particular issue? I saw it looks like the pr is still sitting open. I also have this issue in upgrading to next 12 across all my projects, since they are all using yarn 3.0.2 |
@timneutkens It can be fixed by specifying path like https://github.com/swc-project/swc/blob/9cb3bf96dc26fe80f76bbdb6d89b30368e673778/tests/fixture/config/regenerator/import-path/1/.swcrc |
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?
12.0.2-canary.8
What version of Node.js are you using?
16.3.0
What browser are you using?
Firefox
What operating system are you using?
macOS
How are you deploying your application?
yarn dev
Describe the Bug
Running
yarn build
defined as"build": "next build"
in package.json throws an error in multiple files:Module not found: Can't resolve 'regenerator-runtime' in '/Users/xxx/...'
Expected Behavior
Since I have not changed anything but upgrading Next.js from 11 to 12, I expect it not to fail builds.
To Reproduce
Use yarn 3.0.2 and latest Next.js
The text was updated successfully, but these errors were encountered: