Vercel CLI 33.3.0 broke "vercel deploy --prebuilt" in monorepo: ENOENT lstat node_modules

Vercel CLI 33.3.0 broke "vercel deploy --prebuilt" in monorepo: ENOENT lstat node_modules

The problem

After updating the Vercel CLI to 33.3.0, vercel deploy --prebuilt in a monorepo (Turborepo + pnpm, GitHub Actions with npx vercel) broke with: Error: ENOENT: no such file or directory, lstat '.../dist/apps/APPNAME/nodemodules/styled-jsx/index.js'. A commit in 33.3.0 started checking file paths in .vc-config.json files, incorrectly assuming the .next directory was built in place instead of using the pre-built files - so prebuilt deploys failed as a standalone feature.

The verified fix

This was a regression in Vercel CLI 33.3.0. The confirmed workaround, endorsed by a Vercel maintainer in the thread, is to pin/downgrade the CLI to 33.2.0 until a fixed release lands. Longer-term hygiene from the thread: version-lock the CLI instead of installing vercel@latest in CI - add it as a devDependency and invoke it via npm exec vercel (or npx with a pinned version) so a bad CLI release can't break your pipeline again. Also make sure the .next/ build output (including .next/build-manifest.json) is persisted between your build and deploy jobs, since vercel deploy --prebuilt reads it. Source: https://github.com/vercel/vercel/issues/11097

Asked in the thread (https://vectle.com/threads/thrxyPDxYBVltX82r8rqHo3Q): After updating the Vercel CLI to 33.3.0, vercel deploy --prebuilt in a monorepo (Turborepo + pnpm, GitHub Actions with npx vercel) broke with: Error: ENOENT: no such file or directory, lstat '.../dist/apps/APPNAME/nodemodules/styled-jsx/index.js'. A commit in 33.3.0 started checking file paths in .vc-config.json files, incorrectly assuming the .next directory was built in place instead of using the pre-built files - so prebuilt deploys failed as a standalone feature. The verified answer: This was a regression in Vercel CLI 33.3.0. The confirmed workaround, endorsed by a Vercel maintainer in the thread, is to pin/downgrade the CLI to 33.2.0 until a fixed release lands. Longer-term hygiene from the thread: version-lock the CLI instead of installing vercel@latest in CI - add it as a devDependency and invoke it via npm exec vercel (or npx with a pinned version) so a bad CLI release can't break your pipeline again. Also make sure the .next/ build output (including .next/build-manifest.json) is persisted between your build and deploy jobs, since vercel deploy --prebuilt reads it. Source: https://github.com/vercel/vercel/issues/11097 Thread: https://vectle.com/threads/thrxyPDxYBVltX82r8rqHo3Q