Cannot find module `undici` on initial page load with 500 error code #6900

nickBes · 2024-05-18T10:09:13Z

nickBes
May 18, 2024

Summary

I made a preview deployment of a nextjs app, so my customers could test it during development.
Everything seems to work as expected, except that every time I visit a random page initially, by reloading or entering a URL in the browser, I get the page but with an 500 error code.

Example

No response

Steps to Reproduce

I wish that I knew how to replicate the problem, it seems like a normal nextjs app.
So I'll just attach everything that seems relevant.

Here is the environment on which the code runs:

That's how the logs look like:

Error: Cannot find module 'undici'
Require stack:
- /var/task/.next/server/app/(client)/page.js
- /var/task/node_modules/.pnpm/next@14.2.3_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/next-server/server.runtime.prod.js
- /var/task/___next_launcher.cjs
- /opt/rust/nodejs.js
    at Module._resolveFilename (node:internal/modules/cjs/loader:1143:15)
    at /var/task/node_modules/.pnpm/next@14.2.3_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/next-server/server.runtime.prod.js:11:90905
    at Module._load (node:internal/modules/cjs/loader:984:27)
    at /opt/rust/nodejs.js:1:11508
    at Function.Qt (/opt/rust/nodejs.js:1:11878)
    at Q.e.<computed>.K._load (/opt/rust/nodejs.js:1:11478)
    at Module.require (node:internal/modules/cjs/loader:1231:19)
    at h.require (/var/task/node_modules/.pnpm/next@14.2.3_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/next-server/server.runtime.prod.js:11:91121)
    at require (node:internal/modules/helpers:179:18)
    at 83122 (/var/task/.next/server/app/(client)/page.js:1:1403) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    '/var/task/.next/server/app/(client)/page.js',
    '/var/task/node_modules/.pnpm/next@14.2.3_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/next-server/server.runtime.prod.js',
    '/var/task/___next_launcher.cjs',
    '/opt/rust/nodejs.js'
  ],
  digest: '2504440372'
}

The weird thing about this error is that sometimes the require stack starts with a different page file. For instance, when trying to access /categories/[id], you'd expect that the stack trace would start with /var/task/.next/server/app/categories/[id]/page.js, however it could start with /var/task/.next/server/app/cart/page.js 😕

These are my dependencies:

"dependencies": {
    "@hookform/resolvers": "^3.4.0",
    "@radix-ui/react-dialog": "^1.0.5",
    "@radix-ui/react-popover": "^1.0.7",
    "@react-email/head": "0.0.7",
    "@react-email/html": "0.0.7",
    "@react-email/tailwind": "0.0.14",
    "@t3-oss/env-nextjs": "^0.7.3",
    "@tanstack/react-query": "^5.36.2",
    "@trpc/client": "11.0.0-rc.373",
    "@trpc/react-query": "11.0.0-rc.373",
    "@trpc/server": "11.0.0-rc.373",
    "firebase": "^10.12.0",
    "firebase-admin": "^11.11.1",
    "js-cookie": "^3.0.5",
    "next": "^14.2.3",
    "react": "18.2.0",
    "react-dom": "18.2.0",
    "react-firebase-hooks": "^5.1.1",
    "react-hook-form": "^7.51.4",
    "react-textarea-autosize": "^8.5.3",
    "resend": "^3.2.0",
    "server-only": "^0.0.1",
    "superjson": "^2.2.1",
    "usehooks-ts": "^3.1.0",
    "zod": "^3.23.8"
  },
  "devDependencies": {
    "@firebase/rules-unit-testing": "^3.0.3",
    "@types/eslint": "^8.56.10",
    "@types/js-cookie": "^3.0.6",
    "@types/node": "^18.19.33",
    "@types/react": "^18.3.2",
    "@types/react-dom": "^18.3.0",
    "@typescript-eslint/eslint-plugin": "^6.21.0",
    "@typescript-eslint/parser": "^6.21.0",
    "autoprefixer": "^10.4.19",
    "dotenv": "^16.4.5",
    "eslint": "^8.57.0",
    "eslint-config-next": "^13.5.6",
    "postcss": "^8.4.38",
    "prettier": "^3.2.5",
    "prettier-plugin-tailwindcss": "^0.5.14",
    "tailwind-scrollbar": "^3.1.0",
    "tailwindcss": "^3.4.3",
    "typescript": "^5.4.5",
    "vitest": "^1.6.0"
  },

Answered by yamashhh

Aug 28, 2024

Apparently, v14.2.7 fixed this issue.

https://github.com/vercel/next.js/releases/tag/v14.2.7

The error does not occur even if I remove undici from my dependencies, since I updated to v14.2.7.

View full answer

horiondreher · 2024-05-21T17:23:26Z

horiondreher
May 21, 2024

I'm experiencing the same problem, which started after upgrading to "next": "14.2.3". In my case, the issue occurs whenever I try to access a page with a dynamic route directly, rather than navigating there from a previous page.

For example, if I have a route like myapp.com/[slug]/home, and I navigate directly to "myapp.com/john-doe/home" by pasting the URL into the browser, I get the error: Error: Cannot find module 'undici'. However, if I navigate to this page from another page within the app, the error does not occur.

Additionally, this issue only occurs after deploying to Vercel from the CI; it does not happen locally. I'm not overriding the build command on Vercel, and I'm using Node 20.x.

0 replies

27lakshay · 2024-05-29T19:03:34Z

27lakshay
May 29, 2024

Hey, have you been able to solve the problem, I'm also facing the same error during production deployment

1 reply

horiondreher May 29, 2024

Actually no, I just downgraded the version to "next": "14.1.4" and the issue stopped.

abusada · 2024-06-18T12:39:15Z

abusada
Jun 18, 2024

Facing same issue on production, @nickBes have you found a solution?

0 replies

nghiepdev · 2024-06-18T12:58:21Z

nghiepdev
Jun 18, 2024

I'm experiencing the same issue. It could be related to the firebase package.

0 replies

codercatdev · 2024-06-18T14:41:35Z

codercatdev
Jun 18, 2024

I have run into the same problem, right after adding firebase. I don't see undici show up on the firebase dep tree though?

pnpm ls "undici*" --depth Infinity                                                                             ─╯
Legend: production dependency, optional only, dev only

/Users/afa/web/codercatdev/cms-sanity

dependencies:
@codingcatdev/sanity-plugin-podcast-rss 1.0.0
└─┬ sanity 3.44.0 peer
  ├─┬ @sanity/cli 3.44.0
  │ └─┬ @sanity/codegen 3.44.0
  │   └─┬ globby 10.0.2
  │     └─┬ @types/glob 7.2.0
  │       └─┬ @types/node 20.13.0
  │         └── undici-types 5.26.5
  ├─┬ @sanity/import 3.37.4
  │ └─┬ globby 10.0.2
  │   └─┬ @types/glob 7.2.0
  │     └─┬ @types/node 20.13.0
  │       └── undici-types 5.26.5
  ├─┬ @types/tar-stream 3.1.3
  │ └─┬ @types/node 20.13.0
  │   └── undici-types 5.26.5
  ├─┬ @vitejs/plugin-react 4.3.0
  │ └─┬ vite 4.5.3 peer
  │   └─┬ @types/node 20.13.0 peer
  │     └── undici-types 5.26.5
  └─┬ vite 4.5.3
    └─┬ @types/node 20.13.0 peer
      └── undici-types 5.26.5
@sanity/assist 3.0.4
└─┬ sanity 3.44.0 peer
  ├─┬ @sanity/cli 3.44.0
  │ └─┬ @sanity/codegen 3.44.0
  │   └─┬ globby 10.0.2
  │     └─┬ @types/glob 7.2.0
  │       └─┬ @types/node 20.13.0
  │         └── undici-types 5.26.5
  ├─┬ @sanity/import 3.37.4
  │ └─┬ globby 10.0.2
  │   └─┬ @types/glob 7.2.0
  │     └─┬ @types/node 20.13.0
  │       └── undici-types 5.26.5
  ├─┬ @types/tar-stream 3.1.3
  │ └─┬ @types/node 20.13.0
  │   └── undici-types 5.26.5
  ├─┬ @vitejs/plugin-react 4.3.0
  │ └─┬ vite 4.5.3 peer
  │   └─┬ @types/node 20.13.0 peer
  │     └── undici-types 5.26.5
  └─┬ vite 4.5.3
    └─┬ @types/node 20.13.0 peer
      └── undici-types 5.26.5

5kkug7p43 - broke
eban5fag6 -works

0 replies

nickBes · 2024-06-19T20:21:10Z

nickBes
Jun 19, 2024
Author

I needed a quick solution, so I simply used @horiondreher's tip to downgrade "next": "14.1.4"

Also in my case undici seems to shop up in firebase's dep tree, but not in firebase-admin:

pnpm ls "undici*" --depth Infinity
Legend: production dependency, optional only, dev only

dependencies:
firebase 10.12.2
├─┬ @firebase/auth 1.7.4
│ └── undici 5.28.4
├─┬ @firebase/auth-compat 0.5.9
│ ├─┬ @firebase/auth 1.7.4
│ │ └── undici 5.28.4
│ └── undici 5.28.4
├─┬ @firebase/firestore 4.6.3
│ ├─┬ @grpc/grpc-js 1.9.14
│ │ ├─┬ @grpc/proto-loader 0.7.13
│ │ │ └─┬ protobufjs 7.3.0
│ │ │   └─┬ @types/node 18.19.33
│ │ │     └── undici-types 5.26.5
│ │ └─┬ @types/node 18.19.33
│ │   └── undici-types 5.26.5
│ ├─┬ @grpc/proto-loader 0.7.13
│ │ └─┬ protobufjs 7.3.0
│ │   └─┬ @types/node 18.19.33
│ │     └── undici-types 5.26.5
│ └── undici 5.28.4
└─┬ @firebase/firestore-compat 0.3.32
  └─┬ @firebase/firestore 4.6.3
    ├─┬ @grpc/grpc-js 1.9.14
    │ ├─┬ @grpc/proto-loader 0.7.13
    │ │ └─┬ protobufjs 7.3.0
    │ │   └─┬ @types/node 18.19.33
    │ │     └── undici-types 5.26.5
    │ └─┬ @types/node 18.19.33
    │   └── undici-types 5.26.5
    └─┬ @grpc/proto-loader 0.7.13
      └─┬ protobufjs 7.3.0
        └─┬ @types/node 18.19.33
          └── undici-types 5.26.5

2 replies

horiondreher Jun 19, 2024

That checks out since I am using firebase too

zavbala Aug 9, 2024

Downgrading Next.js to 14.1.4 tailwindcss got break 😭

SaizFerri · 2024-08-03T19:19:19Z

SaizFerri
Aug 3, 2024

I have the same issue on 14.3.0-canary.24. Also using firebase.

0 replies

yamashhh · 2024-08-07T07:22:46Z

yamashhh
Aug 7, 2024

I also had the same issue mentioned here, having firebase as a dependency and not using undici directly in my codebase.
Although it isn't likely to be a fundamental solution, I was able to work around it by adding undici as a dependency in package.json.

0 replies

mathieux51 · 2024-08-13T07:16:50Z

mathieux51
Aug 13, 2024

Same issue in my project, we are also using firebase

0 replies

amyegan · 2024-08-13T21:49:37Z

amyegan
Aug 13, 2024
Maintainer

Can you try Next.js v14.2.5 and let me know if it works for you?

2 replies

zavbala Aug 13, 2024

Installing undici in my package, works for me.

deltaepsilon Aug 17, 2024

This worked for me too. npm install undici

yamashhh · 2024-08-28T06:11:24Z

yamashhh
Aug 28, 2024

Apparently, v14.2.7 fixed this issue.

https://github.com/vercel/next.js/releases/tag/v14.2.7

The error does not occur even if I remove undici from my dependencies, since I updated to v14.2.7.

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Vercel

Cannot find module `undici` on initial page load with 500 error code #6900

{{title}}

Replies: 11 comments 5 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

Cannot find module undici on initial page load with 500 error code #6900

Summary

Example

Steps to Reproduce

Replies: 11 comments · 5 replies

nickBes Jun 19, 2024 Author

amyegan Aug 13, 2024 Maintainer

Cannot find module `undici` on initial page load with 500 error code #6900

Replies: 11 comments 5 replies

nickBes
Jun 19, 2024
Author

amyegan
Aug 13, 2024
Maintainer