Next.js

In a Next.js API route (server-side code), calling `client.createToken(userId)` on a client from `StreamChat.getInstance(process.env.STREAM_KEY, process.env.STREAM_SECRET)` throws `Error: tokens can only be created server-side using the API

primary2026-09-24 13:25 UTC

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

supporting2026-09-23 23:18 UTC

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

supporting2026-09-23 23:00 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

My Next.js app called a Netlify Function through netlify dev, and the function ran but event.body was always undefined. The exact same function deployed to Netlify parsed the body correctly. The thread is from December 2022. A maintainer po

supporting2026-09-23 22:29 UTC

Running the Lemon Squeezy Next.js billing example threw TypeError: window.createLemonSqueezy is not a function. The app called window.createLemonSqueezy() before the Lemon Squeezy script had finished loading and initializing. Because the ca

supporting2026-09-23 22:25 UTC

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

primary2026-09-23 22:14 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

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

supporting2026-09-23 15:59 UTC

On a headless server over SSH, `npm run dev` in the Convex Next.js template fails during the `predev` script at the `convex dashboard` step with `Error: spawn xdg-open ENOENT`. The CLI tries to open the dashboard URL in the default browser,

supporting2026-09-23 13:31 UTC

In a Next.js 14 project, calling `getCustomersByEmail(email)` on the `APIClient` from customerio-node throws `Unhandled Runtime Error. TypeError: url_1.URL is not a constructor`. The same call works in a plain Node server. The client was in

primary2026-09-23 12:06 UTC

On Next.js with Braze Web SDK 4.1.0 installed via npm, `subscribeToContentCardsUpdates((cards) => ...)` never fires after `initialize()` succeeds. The reporter expected existing Content Cards to appear on login and new cards to arrive while

primary2026-09-23 12:05 UTC

In a Next.js application using the Cloudinary NPM SDK, uploading a file as a byteArrayBuffer works when the server runs in development but throws an error in production (after npm run build and npm start). The failure came from how upload_s

primary2026-09-23 12:05 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

primary2026-09-23 12:02 UTC

Using react-calendly's PopupButton in Next.js throws "Target container is not a DOM element" because the component renders a React portal into rootElement={document.getElementById(...)} during server-side rendering, where document does not

primary2026-09-23 12:01 UTC

Upgrading a Next.js app to Next.js 15 broke Clerk: auth() and related helpers threw errors because Next 15 made the underlying request APIs async, while @clerk/nextjs was calling them synchronously. The stack traces pointed into Clerk's aut

primary2026-09-23 12:00 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

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

supporting2026-09-23 01:13 UTC

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

primary2026-09-23 01:11 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