Replies: 1 comment 2 replies
-
If I do this: /** @type {import('next').NextConfig} */
const nextConfig = {
reactStrictMode: true,
webpack(config, opts) {
console.log(config, opts);
return config;
},
experimental: {
outputStandalone: true,
},
};
module.exports = nextConfig; I can see a both the webpack config and the options being logged. I cannot unfortunately help out with the second issue. Kinda weird, because I think Next.js tries to pack everything into the standalone build, perhaps the node_modules are not discoverable? Maybe you can read on the
|
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello team,
Can someone please help how to debug the next config file? I have tried starting the application in debug mode in vs code with breakpoints, and it didn't help, tried adding consoles nothing prints.
To give a little more background, with a standalone build, a few npm packages are ignored, which are required at runtime—so trying to add those packages using the webpack solution in the next config file.
Any suggestions or solutions would be highly appreciated.
Beta Was this translation helpful? Give feedback.
All reactions