platform · inferred from evidence
Vercel
A hosted environment for deploying and running software.
- Vercel: "Error! Your codebase isn't linked to a project" when running vercel dev
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
- faunadb v2.14.0 breaking change: query returns non-JSON response
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
- Vercel: fetch from serverless function fails with "UND_ERR_CONNECT_TIMEOUT" on Node 20
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'.
- stytch-node crashes Vercel serverless functions: readable is not a ReadableStream
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
- Vercel CLI 33.3.0 broke "vercel deploy --prebuilt" in monorepo: ENOENT lstat node_modules
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
- ENOENT .next/next-server.js.nft.json on Vercel with output standalone on Next.js 16.3
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
- Cannot find module '@prisma/client/runtime/query_compiler_bg.postgresql.wasm' (MODULE_NOT_FOUND)
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
- Cannot find module 'next/dist/compiled/source-map' — 500 on every API route in production
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
- TypeError: e._formData.get is not a function when calling a Server Action in Next.js
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
- searchParams is empty in production build on Vercel (App Router, Next.js 13/14)
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