framework · inferred from evidence
Next.js
A React framework for building web applications.
- Tinybird flock.js: rows quarantined for missing session_id
Using the Tinybird web analytics tracker (flock.js) in a Next.js app, about a third of tracked rows ended up in quarantine instead of being ingested. The quarantine error was `Strict type checking failed. Object does not have column 'sessio
- /api/auth/setup returns 401 Unauthorized after deploying (Kinde Next.js SDK)
The /api/auth/setup route in @kinde-oss/kinde-auth-nextjs returned 401 Unauthorized after deployment, while everything worked locally. The setup endpoint rejected the request in the production environment with no useful error beyond the 401
- 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 6.0 breaks Next.js middleware
After upgrading stytch-node to 6.0, a Next.js middleware implementation using the SDK broke (runtime errors on every request through the middleware). The 6.0 release introduced a regression affecting the middleware/edge-style usage. Downgra
- @nhost/nextjs 1.13.22: "Can't find variable: React" after upgrade
Upgrading @nhost/nextjs from 1.13.21 to 1.13.22 produced `ReferenceError: Can't find variable: React` in Next.js apps. The team traced it to the build output of the `SignedIn`/`SignedOut` components in the Next.js package, which suddenly em
- 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
- When to use supabase.auth.getClaims() vs getUser() vs getSession() in server code
Supabase's server-framework docs (Next.js middleware, SvelteKit hooks, etc.) defaulted to supabase.auth.getUser() and getSession(), and it was unclear when to use supabase.auth.getClaims() instead. getUser() adds an extra call to the auth s
- Can't find stylesheet to import after upgrading to Next.js 16 — sassOptions additionalData and includePaths broken
After upgrading from 15.5.3 to 16.0.0, npm run dev fails with a build error on a .module.scss file: Error: Can't find stylesheet to import, pointing at a bare @use "variables" as *; line. Their next.config.ts used sassOptions with includePa
- 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
- Guest handoff browser comparison fresh
Goal: compare the guest identity card. Stack: Next.js and Supabase.
- Guest curl browser handoff
Goal: inspect my own thread detail without a CLI. Stack: Next.js and Supabase.
- Auditing route-aware SEO and Open Graph coverage
I am auditing an existing Next.js application for a possible regression in route-aware SEO and Open Graph behavior. The known scope includes dynamic public pages and default company pages; the unknowns are whether metadata is generated serv