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

Upgrading from 10.0.1 to 10.0.2 causes Error: Cannot find module 'babel-plugin-import' #19641

Closed
nodeworks opened this issue Nov 29, 2020 · 4 comments
Milestone

Comments

@nodeworks
Copy link

Bug report

Describe the bug

Upgrading from Next 10.0.1 -> 10.0.2 causes dev to break:

error - /yarn/v6/npm-next-10.0.3-2bf9a1625dcd0afc8c31be19fc5516af68d99e80-integrity/node_modules/next/dist/client/next-dev.js
Error: Cannot find module 'babel-plugin-import' from '/usr/src/app'

Rolling back to 10.0.1 fixes the issue. Using Yarn PnP and yarn version 1.22.4.

babel-plugin-import is included in my package.json so it's not an issue with that.

To Reproduce

  1. Add babel-plugin-import
  2. Add Next V10.0.2
  3. Try to run next start and see if build fails

Expected behavior

Expected next start to not fail

System information

  • OS: Mac Big Sur
  • Version of Next.js: 10.0.2
  • Version of Node.js: node:14.15.0-alpine (docker)
  • Deployment: next start
@nodeworks nodeworks added the bug Issue was opened via the bug report template. label Nov 29, 2020
@mrtnbroder
Copy link

I'm having the exact same issue and was able to pinpoint this to this release: v10.0.2-canary.1, v10.0.2-canary.0 works fine still. I guess it has to do with the babel-inlining.

@mrtnbroder
Copy link

Linking #19518 as a possible fix.

@Timer Timer added kind: bug and removed bug Issue was opened via the bug report template. labels Jan 4, 2021
@Timer Timer added this to the iteration 16 milestone Jan 4, 2021
@merceyz
Copy link
Contributor

merceyz commented Jan 9, 2021

Fixed in #20586 (v10.0.5-canary.4)

Using Yarn PnP and yarn version 1.22.4.

I'd strongly suggest using V2 for PnP https://yarnpkg.com/getting-started/migration

@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 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants