[ERR_MODULE_NOT_FOUND]: Cannot find package 'nanoid'

[mufteev]

What version of Next.js are you using?

12.0.0

What version of Node.js are you using?

14.18.0

What browser are you using?

Chrome

What operating system are you using?

Windows

How are you deploying your application?

next start

Describe the Bug

Importing package 'nanoid' causes error:

error - unhandledRejection: Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'nanoid' imported from .next\server\pages\datasets\catalog\[catalog_id].js
Did you mean to import nanoid-npm-3.1.30-58cf6fe7ec-276d0d4b0c.zip/node_modules/nanoid/index.cjs?

package.json dependencies:
"nanoid": "^3.1.30"

Expected Behavior

Successful import

To Reproduce

Occurs when:
yarn version 3.1.0 [berry] - without dir node_modules (only /.yarn/cache) and PnP

• yarn dev
• yarn build

Minimal reproduce in https://github.com/mufteev/BUG-debugging-with-new-line-in-template-literals

[rtritto]

This error is related to SWC.
Same problem with latest version 4.0.0 of node-html-parser dependency.
Correctly work with previous version 3.1.0 or using Babel.

Steps to reproduce:

1. yarn init -y
2. yarn set version berry
3. yarn add next react react-dom node-html-parser
4. Create pages/index.js

import 'node-html-parser'

5. yarn next
6. Go to localhost:3000

Output:

unhandledRejection: Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'node-html-parser' imported from C:\test-nextjs\.next\server\pages\index.js
Did you mean to import node-html-parser-npm-5.0.0-719fdf923f-7fa49cf47b.zip/node_modules/node-html-parser/dist/index.js?

[mward-sudo]

See related issue #30393 with a full reproduction, same issue when using highlight.js package.

[mufteev]

Update reference on minimal reproduce, the principle is similar to #30393.

Minimal reproduction is combined with #30435.

@ijjk

[rtritto]

In my case, node-html-parser is in ESM, so I added "type": "module" in package.json and pnpEnableEsmLoader: true to yarnrc.yml (default value is false but maybe is optional because yarn, on install, autogenerate .pnp.loader.mjs).

Actual result:

[ERR_REQUIRE_ESM]: Must use import to load ES Module: C:\test-nextjs\.next\server\pages\_document.js
require() of ES modules is not supported.
require() of C:\test-nextjs\.next\server\pages\_document.js from C:\test-nextjs\.yarn\__virtual__\next-virtual-4abf088994\0\cache\next-npm-12.0.2-canary.8-0c66f38afe-39035a5d0e.zip\node_modules\next\dist\server\require.js is an ES module file as it is a .js file whose nearest parent package.json contains "type": "module" which defines all .js files in that package scope as ES modules.
Instead rename _document.js to end in .cjs, change the requiring code to use import(), or remove "type": "module" from C:\test-nextjs\package.json.

    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1085:13)
    at Module.load (internal/modules/cjs/loader.js:933:32)
    at Function.external_module_.Module._load (C:\test-nextjs\.pnp.cjs:13417:14)
    at Module.require (internal/modules/cjs/loader.js:957:19)
    at require (internal/modules/cjs/helpers.js:88:18)
    at Object.requirePage (C:\test-nextjs\.yarn\__virtual__\next-virtual-4abf088994\0\cache\next-npm-12.0.2-canary.8-0c66f38afe-39035a5d0e.zip\node_modules\next\dist\server\require.js:48:12)
    at Object.loadComponents (C:\test-nextjs\.yarn\__virtual__\next-virtual-4abf088994\0\cache\next-npm-12.0.2-canary.8-0c66f38afe-39035a5d0e.zip\node_modules\next\dist\server\load-components.js:56:23)
    at DevServer.findPageComponents (C:\test-nextjs\.yarn\__virtual__\next-virtual-4abf088994\0\cache\next-npm-12.0.2-canary.8-0c66f38afe-39035a5d0e.zip\node_modules\next\dist\server\next-server.js:1193:63)
    at DevServer.findPageComponents (C:\test-nextjs\.yarn\__virtual__\next-virtual-4abf088994\0\cache\next-npm-12.0.2-canary.8-0c66f38afe-39035a5d0e.zip\node_modules\next\dist\server\dev\next-dev-server.js:643:26)
    at async DevServer.renderErrorToResponse (C:\test-nextjs\.yarn\__virtual__\next-virtual-4abf088994\0\cache\next-npm-12.0.2-canary.8-0c66f38afe-39035a5d0e.zip\node_modules\next\dist\server\next-server.js:1663:26) {
  code: 'ERR_REQUIRE_ESM'
}

Versions:

next: 12.0.2-canary.8
yarn: 3.1.0

Maybe next.js actually isn't fully compatible with ESM (source)

FYI @timneutkens

---

Edit 1

Same behavior using nanoid or highlight.js.

Edit 2

Next.js doesn't support "type": "module" (yet) (source)

[ericvera]

FYI, while this gets fixed I was able to get unblocked by adding experimental: { esmExternals: false }, to next.config.js as suggested in #30873.

[kmvan]

FYI, while this gets fixed I was able to get unblocked by adding experimental: { esmExternals: false }, to next.config.js as suggested in #30873.

Which package?

[kmvan]

I think this is a Node bug. Meet it with only node app.

[rtritto]

@balazsorban44 @timneutkens This issue can be closed.

[github-actions]

Please verify that your issue can be recreated with next@canary.

Why was this issue marked with the please verify canary label?

We noticed the provided reproduction was using an older version of Next.js, instead of canary.

The canary version of Next.js ships daily and includes all features and fixes that have not been released to the stable version yet. You can think of canary as a public beta. Some issues may already be fixed in the canary version, so please verify that your issue reproduces by running npm install next@canary and test it in your project, using your reproduction steps.

If the issue does not reproduce with the canary version, then it has already been fixed and this issue can be closed.

How can I quickly verify if my issue has been fixed in canary?

The safest way is to install next@canary in your project and test it, but you can also search through closed Next.js issues for duplicates or check the Next.js releases. You can also use the GitHub template (preferred), or the CodeSandbox or StackBlitz templates to create a reproduction with canary from scratch.

My issue has been open for a long time, why do I need to verify canary now?

Next.js does not backport bug fixes to older versions of Next.js. Instead, we are trying to introduce only a minimal amount of breaking changes between major releases.

What happens if I don't verify against the canary version of Next.js?

An issue with the please verify canary that receives no meaningful activity (e.g. new comments that acknowledge verification against canary) will be automatically closed and locked after 30 days.

If your issue has not been resolved in that time and it has been closed/locked, please open a new issue, with the required reproduction, using next@canary.

I did not open this issue, but it is relevant to me, what can I do to help?

Anyone experiencing the same issue is welcome to provide a minimal reproduction following the above steps. Furthermore, you can upvote the issue using the 👍 reaction on the topmost comment (please do not comment "I have the same issue" without repro steps). Then, we can sort issues by votes to prioritize.

I think my reproduction is good enough, why aren't you looking into it quicker?

We look into every Next.js issue and constantly monitor open issues for new comments.

However, sometimes we might miss one or two due to the popularity/high traffic of the repository. We apologize, and kindly ask you to refrain from tagging core maintainers, as that will usually not result in increased priority.

Upvoting issues to show your interest will help us prioritize and address them as quickly as possible. That said, every issue is important to us, and if an issue gets closed by accident, we encourage you to open a new one linking to the old issue and we will look into it.

Useful Resources

• How to Contribute to Open Source (Next.js)
• How to create a Minimal, Complete, and Verifiable example
• Reporting a Next.js bug
• Next.js Triaging issues

[github-actions]

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.