Module not found: Can't resolve 'regenerator-runtime' -- after upgrading from 11 to 12.0.2-canary.8
See original GitHub issueWhat 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
Issue Analytics
- State:
- Created 2 years ago
- Reactions:4
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Babel and Webpack are throwing "Can't resolve ' ...
Installing regenerator-runtime did not help, and I thought the issue lied in Yarn's pnp modules: This dependency was not found: ...
Read more >regenerator-runtime
Runtime for Regenerator-compiled generator and async functions. ... Start using regenerator-runtime in your project by running `npm i ...
Read more >vue__webpack_imported_modul...
I am only a learner of Vue in very early stage. Cannot figure out how I can resolve these issues, especially with the...
Read more >How to fix regeneratorRuntime is not defined?
First, I found this solution: add import "babel-polyfill"; at the top of the file that you are using the async function. BUT.
Read more >Blank Admin Page: regeneratorRuntime is not defined ...
I also have this issue! I got the issue deploying with Heroku. When I updated strapi and made a new strapi project, it...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@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
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.