next.js: Missing webpack dependency when using output standalone + custom server
Link to the code that reproduces this issue
https://github.com/maximelebastard/nextjs-issue-custom-server
To Reproduce
The issue is related to using the output: “standalone” with a custom server. See example repository.
- Clone the reproducing repository
- Run
npm installthennpm run buildandnpm run start - When starting the app, an error will be triggered due to a missing webpack file on a webpack require (see the error below)
- To see the code triggering this issue, see this commit: https://github.com/maximelebastard/nextjs-issue-custom-server/commit/c47de3a03c6694ac760b748ed2fecc28b97bb2e5
Current vs. Expected behavior
Expected:
- I create a recent NextJS project (14.1.4) using a recent Node version (v20.12)
- I want to deploy my app using Docker, therefore I use the
output: "standalone"configuration innext.config.js - I want to use some logging middlewares, therefore I use a custom
server.js - When I run
npm run buildand copy my custom server code to the build dir, the app is properly built and the file is properly copied - When requiring next from
server.js, all the dependencies are present and the server starts
Actual:
- 1-4 are the same as expected
.next/standalone/node_modules/next/dist/compiled/webpack/build5.jsdoes not exists in the built app- When requiring next from
server.js, I’m getting the error below because webpack tries to requirebuild5.js
> node .next/standalone/custom-server.js
node:internal/modules/cjs/loader:1143
const err = new Error(message);
^
Error: Cannot find module './bundle5'
Require stack:
- /Users/maxime/workspace/issue-bundle5-nextjs/.next/standalone/node_modules/next/dist/compiled/webpack/webpack.js
- /Users/maxime/workspace/issue-bundle5-nextjs/.next/standalone/node_modules/next/dist/server/config-utils.js
- /Users/maxime/workspace/issue-bundle5-nextjs/.next/standalone/node_modules/next/dist/server/config.js
- /Users/maxime/workspace/issue-bundle5-nextjs/.next/standalone/node_modules/next/dist/server/next.js
- /Users/maxime/workspace/issue-bundle5-nextjs/.next/standalone/custom-server.js
at Module._resolveFilename (node:internal/modules/cjs/loader:1143:15)
at /Users/maxime/workspace/issue-bundle5-nextjs/.next/standalone/node_modules/next/dist/server/require-hook.js:55:36
at Module._load (node:internal/modules/cjs/loader:984:27)
at Module.require (node:internal/modules/cjs/loader:1231:19)
at mod.require (/Users/maxime/workspace/issue-bundle5-nextjs/.next/standalone/node_modules/next/dist/server/require-hook.js:65:28)
at require (node:internal/modules/helpers:179:18)
at exports.init (/Users/maxime/workspace/issue-bundle5-nextjs/.next/standalone/node_modules/next/dist/compiled/webpack/webpack.js:24:28)
at loadWebpackHook (/Users/maxime/workspace/issue-bundle5-nextjs/.next/standalone/node_modules/next/dist/server/config-utils.js:18:5)
at loadConfig (/Users/maxime/workspace/issue-bundle5-nextjs/.next/standalone/node_modules/next/dist/server/config.js:642:46)
at initialize (/Users/maxime/workspace/issue-bundle5-nextjs/.next/standalone/node_modules/next/dist/server/lib/router-server.js:55:46) {
code: 'MODULE_NOT_FOUND',
requireStack: [
'/Users/maxime/workspace/issue-bundle5-nextjs/.next/standalone/node_modules/next/dist/compiled/webpack/webpack.js',
'/Users/maxime/workspace/issue-bundle5-nextjs/.next/standalone/node_modules/next/dist/server/config-utils.js',
'/Users/maxime/workspace/issue-bundle5-nextjs/.next/standalone/node_modules/next/dist/server/config.js',
'/Users/maxime/workspace/issue-bundle5-nextjs/.next/standalone/node_modules/next/dist/server/next.js',
'/Users/maxime/workspace/issue-bundle5-nextjs/.next/standalone/custom-server.js'
]
}
Provide environment information
Operating System:
Platform: darwin
Arch: arm64
Version: Darwin Kernel Version 23.1.0: Mon Oct 9 21:27:24 PDT 2023; root:xnu-10002.41.9~6/RELEASE_ARM64_T6000
Binaries:
Node: 20.12.0
npm: 10.5.0
Yarn: N/A
pnpm: N/A
Relevant Packages:
next: 14.1.4
eslint-config-next: N/A
react: 18.2.0
react-dom: 18.2.0
typescript: N/A
Next.js Config:
output: standalone
Which area(s) are affected? (Select all that apply)
Standalone mode (output: “standalone”)
Which stage(s) are affected? (Select all that apply)
next start (local)
Additional context
A workaround I found is to disable standalone output. That probably disables tree shaking and relies on the complete node_modules directory. A big drawback is that it makes a heavy docker image.
About this issue
- Original URL
- State: open
- Created 3 years ago
- Reactions: 19
- Comments: 18 (4 by maintainers)
Commits related to this issue
- Support custom servers with minimal node modules (#72966) ## Fixing a bug ### Related issues fixes #64031 ### Why is this change needed Per the Next.js [docs](https://nextjs.org/docs/pages/api-re... — committed to vercel/next.js by MJez29 2 years ago
- Support custom servers with minimal node modules (#72966) ## Fixing a bug ### Related issues fixes #64031 ### Why is this change needed Per the Next.js [docs](https://nextjs.org/docs/pages/api-re... — committed to vercel/next.js by MJez29 2 years ago
I have same issue. And I found the server.js which compiled with standalone can works. So I just copy these 2lines, and my custom server.js also works fine.
Here’s my code, and while it works successfully, I’m not sure it’s going to be a hidden problem
Thanks @nectoscorp
After I tested, it works 😂
I’ve met, too, frustrating
I also ran into this issue and came up with the exact same fix
I put up a PR to fix this in next.js: https://github.com/vercel/next.js/pull/72966
I confirmed that this works for me: https://github.com/vercel/next.js/issues/64031#issuecomment-2078708340 So AWS lambda, I am using the following to extract the JSON:
sed -n 12p .next/standalone/server.js | cut -c 20-then require it inside my lambda handler file.
If I had more time I will figure out which particular parameter in the config made it work by commenting them out one at a time.