Missing webpack dependency when using output standalone + custom server #64031
Comments
github-actions
bot
added
the
Output (export/standalone)
maximelebastard
changed the title
This comment has been minimized.
This comment has been minimized.
|
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 import { createServer } from 'node:http';
import { parse } from 'node:url';
import NextServer from 'next/dist/server/next-server';
// @ts-ignore
import { config } from './.next/required-server-files.json';
import { NextConfig } from 'next';
const port = parseInt(process.env.PORT || '9000', 10);
const hostname = '0.0.0.0';
const dev = process.env.NODE_ENV !== 'production';
const app = new NextServer({
hostname: 'localhost',
port,
dir: process.cwd(),
dev,
conf: {
...(config as NextConfig),
},
});
const handle = app.getRequestHandler();
app.prepare().then(() => {
createServer((req, res) => {
try {
const parsedUrl = parse(req.url!, true);
handle(req, res, parsedUrl);
} catch (err) {
console.error('Error occurred handling', req.url, err);
res.statusCode = 500;
res.end('internal server error');
}
})
.once('error', (err) => {
logger.error(err);
process.exit(1);
})
.listen(port, () => {
console.log(
`> Server listening at http://${hostname}:${port} as ${
dev ? 'development' : process.env.NODE_ENV
}`,
);
});
}); |
|
I've met, too, frustrating Node.js v18.20.2
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
yarn run v1.22.19
$ NODE_ENV=production node ./server/main.js
node:internal/modules/cjs/loader:1140
const err = new Error(message);
^
Error: Cannot find module './bundle5'
Require stack: |
|
Already 3 months passed, there is still no any progress? 🫠 |
This comment has been minimized.
This comment has been minimized.
|
I confirmed that this works for me: #64031 (comment) 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. |
Thanks @nectoscorp After I tested, it works 😂 |
|
I wish the nextConfig json was just saved on a file in like |
|
Having the same issue. This seems to work well for me to allow for both local dev development and docker deployment: const dev = process.env.NODE_ENV !== 'production'
if (!dev) {
// eslint-disable-next-line @typescript-eslint/no-require-imports
const { config } = require('./.next/required-server-files.json')
process.env.__NEXT_PRIVATE_STANDALONE_CONFIG = JSON.stringify(config)
} |
The ES6-conform version: |
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.
npm installthennpm run buildandnpm run startCurrent vs. Expected behavior
Expected:
output: "standalone"configuration innext.config.jsserver.jsnpm run buildand copy my custom server code to the build dir, the app is properly built and the file is properly copiedserver.js, all the dependencies are present and the server startsActual:
.next/standalone/node_modules/next/dist/compiled/webpack/build5.jsdoes not exists in the built appserver.js, I'm getting the error below because webpack tries to requirebuild5.jsProvide 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: standaloneWhich 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.
The text was updated successfully, but these errors were encountered: