Vercel

After upgrading the CLI, running vercel dev failed with: Error! Your codebase isn't linked to a project on Vercel. Run `vercel` to link it. The reporter did not want to deploy just to develop locally. A maintainer confirmed this is intended

primary2026-09-23 23:20 UTC

After upgrading the faunadb driver from 2.13.0 to 2.14.0, my queries started returning something that wasnt JSON in a Vercel serverless function, while the exact same code worked fine on 2.13.0. Another user on Vercel confirmed the same beh

supporting2026-09-23 22:52 UTC

A Next.js 14 app on Vercel (Node 20.x) making fetch calls from serverless functions to external APIs (Slack, Neon, etc.) intermittently failed with TypeError: fetch failed ... cause: ConnectTimeoutError ... code: 'UND_ERR_CONNECT_TIMEOUT'.

primary2026-09-23 22:42 UTC

Using stytch-node inside Vercel serverless functions crashed with Unhandled Promise Rejection: TypeError: First parameter has member 'readable' that is not a ReadableStream. The same code worked locally and in a normal Node VM. The cause wa

primary2026-09-23 22:38 UTC

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/APP_NAME/node_modules/styled-jsx/i

supporting2026-09-23 22:18 UTC

My Next.js 13 project uses the Notion client and builds fine locally, but the Vercel deployment fails with: `Module not found: Can't resolve 'encoding' in '.../node_modules/node-fetch/lib'`. I am on Notion SDK 2.2.2 with Node 16/18. Did Nex

primary2026-09-23 21:41 UTC

Since @upstash/redis v1.14.0, running on Node 14 (e.g. Vercel with the Node 14.x option) throws `Unable to decode base64 []: atob is not defined` when reading values. Cause: v1.14.0 introduced base64 decoding via `atob`, which only exists i

supporting2026-09-23 13:14 UTC

Integrating @axiomhq/nextjs into a Next.js 15 project following the official docs, the Vercel production build fails with: Module build failed: UnhandledSchemeError: Reading from "node:crypto" is not handled by plugins (Unhandled scheme). T

supporting2026-09-23 12:02 UTC

I deployed my D-ID agent app on Vercel and now the agent does not load. The console shows: Access to fetch at api.d-id.com has been blocked by CORS policy, no Access-Control-Allow-Origin header is present. I am using Vite and React.

primary2026-09-23 12:01 UTC

They upgraded to Next.js 16.3 and added output: 'standalone' to next.config.ts. The build compiles and generates static pages fine, then fails at "Running onBuildComplete from Vercel" with Error: ENOENT: no such file or directory, open '/ve

primary2026-09-23 01:15 UTC

Deploying a Prisma 6/7 app fails at runtime with Cannot find module '@prisma/client/runtime/query_compiler_bg.postgresql.wasm' (code MODULE_NOT_FOUND) even though it works locally. Reported on Vercel and in Docker. Two distinct causes surfa

supporting2026-09-23 01:12 UTC

No errors in development, but after deploying to Vercel every API route returns 500 Internal Server Error. Vercel logs show: Cannot find module 'next/dist/compiled/source-map'. Nothing in package.json references source-map directly. Reporte

primary2026-09-23 01:11 UTC

Calling a server action from a client component throws TypeError: e._formData.get is not a function. It happens on the dev server (sometimes after edits or page refreshes, after which all server actions stay broken) and some reporters saw i

supporting2026-09-23 01:11 UTC

On an App Router page with a dynamic route, searchParams works in next dev but arrives empty on Vercel production. One reporter logged searchParams on /user/1?test=1 and /blog/1?test=1: present on one route, absent on the other. It does not

primary2026-09-23 01:11 UTC