Upgrading nextjs v9.3.0 to v.9.3.1 causes Error: Cannot find module 'babel-types'
See original GitHub issueBug report
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
- On an existing nextjs v9.3.0 application
- Bump nextjs to v9.3.1
npm install next@latest - run dev
next dev
Expected behavior
expected a smooth upgrade
Screenshots
[ error ] ./node_modules/next/dist/client/next-dev.js
[1] Error: Cannot find module 'babel-types'
System information
- OS: macOS
- Version of Next.js: 9.3.1
- @babel/core": “^7.8.7”
- using
.babelrcwithnext/babelpreset
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
8.1.1-canary.70 - next - npm
TypeScript icon, indicating that this package has built-in type declarations. 8.1.1-canary.70 • Public • Published 3 years ago.
Read more >reaviz | Yarn - Package Manager
Data visualization library for React Open Collective backers and sponsors. REAVIZ is a modular chart component library that leverages React natively for ...
Read more >Changelog - Cypress Documentation
Fixed an 11.0.0 regression where using custom reporters would cause Cypress to throw a 'Cannot find module' error. Fixes #24607; Fixed testIsolation ...
Read more >Keysight KCOS 9.30 Third Party & Open-Source License ...
Page 3. December 2022. All rights reserved. @assemblyscript/loader 0.10.1 : Apache License 2.0. @babel/code-frame 7.10.4 : MIT License.
Read more >no exact matches in call to instance method 'map' - You.com | The ...
This is a general error message for using the wrong type in the method calls. ... checkout 3c86d2b Library/Formula/postgresql.rb 9.3.1 git checkout a267a3e ......
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 Free
Top 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

Yep sure, could be that there’s already an open one.
Going to close this issue as it’s not related to Next.js, and we can’t change anything here. Basically your app worked accidentally previously as that babel plugin was hoisting babel-types.
I’m seeing some node-gyp errors… I’ll verify and come up with a complete repro