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

[nickBes]

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"
  },

[horiondreher]

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.

[27lakshay]

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

[horiondreher]

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