Build stuck on runAfterProductionCompile
Unanswered
Devon Rex posted this in #help-forum
Devon RexOP
Hello,
I've upgraded to the version 16.0.3 and I am using vercel to build my nextjs app in standalone mode.
However since the update, I am getting my build stuck quite often (6 times out of 10) on the
any idea what happened?
I've tried with
build is perfectly working locally
Thanks in advance 🙏
I've upgraded to the version 16.0.3 and I am using vercel to build my nextjs app in standalone mode.
However since the update, I am getting my build stuck quite often (6 times out of 10) on the
Running next.config.js provided runAfterProductionCompile ... stepany idea what happened?
I've tried with
pnpm build and pnpm build --turbopack but same issue and vercel is stopping the build automatically after 45mins> NODE_OPTIONS=--max-old-space-size=6144 next build
▲ Next.js 16.0.3 (Turbopack)
- Experiments (use with caution):
· clientTraceMetadata
· optimizePackageImports
Creating an optimized production build ...
Turbopack build encountered 2 warnings:
./node_modules/.pnpm/@opentelemetry+instrumentation@0.204.0_@opentelemetry+api@1.9.0/node_modules/@opentelemetry/instrumentation/build/esm/platform/node
Package require-in-the-middle can't be external
The request require-in-the-middle matches serverExternalPackages (or the default list).
The request could not be resolved by Node.js from the project directory.
Packages that should be external need to be installed in the project directory, so they can be resolved from the output files.
Try to install it into the project directory by running npm install require-in-the-middle from the project directory.
✓ Compiled successfully in 86s
Running next.config.js provided runAfterProductionCompile ...build is perfectly working locally
Thanks in advance 🙏
1 Reply
Devon RexOP
nevermind, that was sentry sourcemap upload which was super slow and timing out