Open maximelebastard opened 7 months ago
cs-miller
commented
6 months ago I'm seeing the same issue
Edit by maintainer bot: Comment was automatically minimized because it was considered unhelpful. (If you think this was by mistake, let us know). Please only comment if it adds context to the issue. If you want to express that you have the same problem, use the upvote 👍 on the issue description or subscribe to the issue for updates. Thanks!
clementzhao
commented
6 months 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.
const nextConfig = {which from compiled server.js}
process.env.__NEXT_PRIVATE_STANDALONE_CONFIG = JSON.stringify(nextConfig)
hi-zp
commented
6 months ago 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
}`,
);
});
});
wq93
commented
6 months ago 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:
yunsii
commented
4 months ago Already 3 months passed, there is still no any progress? 🫠
yunsii
commented
4 months ago Even use v14.2.4 still has the same error...
Edit by maintainer bot: Comment was automatically minimized because it was considered unhelpful. (If you think this was by mistake, let us know). Please only comment if it adds context to the issue. If you want to express that you have the same problem, use the upvote 👍 on the issue description or subscribe to the issue for updates. Thanks!
nectoscorp
commented
4 months ago 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.
yunsii
commented
4 months 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.
const nextConfig = {which from compiled server.js} process.env.__NEXT_PRIVATE_STANDALONE_CONFIG = JSON.stringify(nextConfig)
Thanks @nectoscorp
After I tested, it works 😂
nectoscorp
commented
4 months ago I wish the nextConfig json was just saved on a file in like .next/standalone/next.config.json so we don't have to resort to these hacks. But obviously, the best is solution is to find out why bundle5 couldn't be found.
Brandawg93
commented
2 months ago 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)
}
flawnn
commented
1 month ago 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:
import("./.next/required-server-files.json")
.then(({ default: { config } }) => {
process.env.__NEXT_PRIVATE_STANDALONE_CONFIG = JSON.stringify(config);
const app = next({ dev });
return app.prepare().then(() => startServer(app) // startup func);
})
.catch((error) => {
console.error("Failed to load required-server-files.json:", error);
process.exit(1);
});
SujithPriyamRajan
commented
1 month ago I have the same issue but surprisingly in PM2 as local & VM's was working fine
Can anyone summarize why this issue is ??
/** @type {import('next').NextConfig} */
const nextConfig = {
output: 'standalone',
typescript: {
ignoreBuildErrors: true
},
images: { unoptimized: true },
experimental: {
serverActions: {
serverActions: true
},
missingSuspenseWithCSRBailout: false
},
distDir: 'out',
rewrites: async () => {
return [
{
source: '/_next/static/:path*',
destination: '/static/:path*'
}
];
}
};
export default nextConfig;
aczekajski
commented
1 month ago I found a universal way if adding missing dependencies to standalone output that I guess can also be used for custom server.
You can have a look here: https://github.com/vercel/next.js/discussions/66327#discussioncomment-10889930
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
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.