Skip to content
Problems.

Vercel users keep filing bugs

DevOps and infra6 posts from 6 people4d active+33 posts in the last 7 days, 0 the 7 days before (rising)

Posts per day

Posts per day6 posts, Sep 1 to Sep 25

The posts behind it

6, newest first
PostDate
Turbopack scope hoisting: a circular import inside a merged factory captures a partial namespace, so a client transition crashes while a hard load of the same URL works...Webpack is unaffected because its namespace objects are live getters, not snapshots. The failing edge is the same in every tree we built; only the entry module changes. Swapping components does not avoid it, because the order of entry is what matters. ### Workaround Measured...vercel/next.jsMrMuathXSep 232 days ago
sitemap.ts with `export const revalidate` is emitted as a static file in adapter outputs, so it is never regenerated on Vercel...- Workaround: `await connection()` in `sitemap.ts`. This makes it fully dynamic instead of ISR. - I have a fix with a test ready and will open a PR.vercel/next.jsproply-jpSep 223 days ago
notFound() serves an empty body in production; an unmatched URL serves not-found.tsx### Link to the code that reproduces this issue Minimal reproduction, App Router, four lines: With `app/not-found.tsx` present, run `next build && next start`, then: ### To Reproduce 1. Add the page above and any `not-found.tsx`. 2. `next build && next start` (production - this...vercel/next.jsfoundationalframeworkSep 205 days ago
searchParams promise throws "TypeError: The .constructor property is not an object" when a query key is named `constructor`### Link to the code that reproduces this issue No repository needed - the minimal reproduction is a 6-line Node script (below), because the crash is native V8 behavior triggered by how Next.js constructs the `searchParams` promise. ### To Reproduce 1. Any App Router page that...vercel/next.jsjpatel900Sep 13 weeks ago
Turbopack: a worker emitted via new Worker(new URL('./x.mjs', import.meta.url)) keeps an unrewritten sibling import, so the worker never loads...the same source correctly (details below - with a caveat that matters). ## Why it is hard to diagnose ⚠️ **The `Worker` constructor succeeds.** The module-load failure arrives asynchronously on `worker.onerror`, **with an empty message**. MapLibre does not forward that to its...vercel/next.jsderbederrrSep 13 weeks ago
Cache Components: app-shell prefetch (next-router-prefetch: 3) misses 'use cache' calls keyed on a root param, with no fill ever attempted### Link to the code that reproduces this issue None yet. This is observed and fully traced (stack frames, debug logs, three independent builds - see below) in a private production app, but I have not yet isolated it into a standalone public repo - see "Isolation attempt" below,...vercel/next.jsjuancp92Sep 13 weeks ago

Companies and products named

Company or productPosts naming it
Vercel6
GitHub1
npm1
About this problem

Evidence

6 posts from 6 people in 1 place, about 2 a week over 23 days. Mostly on vercel/next.js. Tools named alongside: GitHub, npm.

Frustration Frustration 0 of 3· Seen on GitHub issues

How it was grouped

Posts about Vercel that state a pain but match no known issue yet. First post Sep 1, 2026, latest Sep 23, 2026. Corroborated: 3 or more posts from 2 or more people or places. Method

History

  • 2026-09-25 Statement: Vercel users keep asking for help to Vercel users keep filing bugs
  • 2026-09-25 Added: Vercel users keep asking for help (6 posts)

Rising problems by email

Mondays: the problems in data, tech and AI that grew fastest that week.

Double opt-in. Unsubscribe any time.