Next.js webpack builds bake absolute paths into server chunks, breaking relocated deploys #23266
Description
next build with webpack emits absolute build-machine paths into .next/server/**:
require("/vercel/path0/node_modules/.../@sentry/server-utils/build/cjs/orchestrion/index.js")Any deploy that relocates the output — Vercel (/vercel/path0 → /var/task), Docker multi-stage, output: 'standalone' — turns these into MODULE_NOT_FOUND on the first request to a dynamic route. Static routes still work, so the build looks healthy.
Activity
linear-code commentedon Aug 11, 2026
JS-3343
fix(nextjs): Stop baking absolute paths into server chunks (getsentry…
fix(nextjs): Stop baking absolute paths into server chunks (#23267)
test(e2e): Add Next.js standalone output test app (#23679)
github-actions commentedon Sep 23, 2026
A PR closing this issue has just been released 🚀
This issue was referenced by PR #23267, which was included in the 11.0.0 release.