Problemsby IbisTrouble with Vercel turbopack
DevOps and infra2 posts from 2 people2d active+00 posts in the last 7 days, 0 the 7 days before (fading)Unverified
Posts per day
The posts behind it
2, newest firstTurbopack 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.js · MrMuathX1 repliesOpen ↗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.js · derbederrr1 repliesOpen ↗
Companies and products named
About this problem
Evidence
2 posts from 2 people in 1 place, about 1 a week over 23 days. Mostly on vercel/next.js.
Frustration Frustration 0 of 3· Seen on GitHub issues
How it was grouped
Posts about Vercel with no known issue, sharing the word "turbopack". First post Sep 1, 2026, latest Sep 23, 2026. Unverified: fewer than 3 posts, or one person or place only. Method
Other Vercel problems
History
Trouble with Vercel turbopack (2 posts)