📋 Open-issue triage & priority index

[hyf0]

A scannable map of the open issues. Every open issue is labeled on three axes:

• Priority — P0: blocker · P1: high · P2: medium · P3: low
• Area — area: dev · area: deploy · area: config · area: build · area: static
• Upstream status — upstream: unfiled (needs filing on cloudflare/vinext) · upstream: has-PR (a vinext PR already exists) · upstream: roadmap (tracked upstream, architectural) · upstream: app-owned (keep the app workaround; not a vinext fix)

Most of these are vinext gaps found while porting react.dev; a few are legitimately app-owned. Grouped by priority below.

---

🔴 P0 — Blocker

• Pages Router: getStaticProps runs per-request instead of prerendering → fs-backed SSG apps 500 on Cloudflare Workers (needs --prerender-all) #15 — getStaticProps runs per-request on Workers (no fs) → every SSG route 500s on deploy. Root of the deploy cluster; also kills client-side <Link> nav on the deploy (hard reloads). Genuine blocker but the fix is architectural — tracked upstream in Static pre-rendering at build time cloudflare/vinext#9 → Populating remote cache during deployment cloudflare/vinext#562 (populate the remote cache from prerendered assets at deploy). Same class: Pages Router: getServerSideProps SSR returns 500 Internal Server Error cloudflare/vinext#1458 (getServerSideProps 500 on Workers); Pages Router: _next/data JSON endpoint not implemented cloudflare/vinext#1330 (_next/data endpoint not implemented → the deploy's hard-reload nav). area: deploy · upstream: roadmap

🟠 P1 — High (real bug, cheap, do soon)

• tsconfig baseUrl bare imports (no paths) are not resolved → ERR_MODULE_NOT_FOUND at SSR #4 — tsconfig baseUrl bare imports not resolved from .js/.jsx files. Every page 500s (Cannot find module 'components/...'). Completely untracked upstream; small self-contained fix. area: config · upstream: unfiled
• vinext dev SSR module-runner doesn't CJS-interop UMD/CJS deps (classnames window, parse-numeric-range exports) #6 — vinext dev can't CJS/UMD-interop raw deps (classnames → window is not defined, parse-numeric-range → exports is not defined). Broadest dev bug; fix already written in fix: support CommonJS node_modules in Pages Router dev cloudflare/vinext#665 (stalled 3+ months on a 1-line Windows path fix). area: dev · upstream: has-PR
• Tracking: vinext dev is unusable for this app — every route 404s (workerd/no-fs) or 500s (dev module-runner can't CJS-interop the per-request MDX compile chain) #16 — (umbrella) vinext dev unusable — 404 or 500 on every route. Two halves: the 404 (cloudflare() + no-fs in dev, already worked around by gating the plugin to deploy) and the 500 (= vinext dev SSR module-runner doesn't CJS-interop UMD/CJS deps (classnames window, parse-numeric-range exports) #6). Effectively resolves once vinext dev SSR module-runner doesn't CJS-interop UMD/CJS deps (classnames window, parse-numeric-range exports) #6 lands. Upstream: SSR dev server fails with "module is not defined" for CJS dependencies (void-elements, highlight.js, etc.) cloudflare/vinext#585 + fix: support CommonJS node_modules in Pages Router dev cloudflare/vinext#665 (the CJS half); Pages Router: _next/data JSON endpoint not implemented cloudflare/vinext#1330 (_next/data). area: dev

🟡 P2 — Medium

• experimental.reactCompiler: true is silently dropped (no warning, no transform) #10 — experimental.reactCompiler silently dropped (no warn, no transform). The mechanism already ships in @vitejs/plugin-react (reactCompilerPreset). area: build · upstream: unfiled
• Static server: .xml / .webmanifest served as application/octet-stream (missing MIME entries) #11 — .xml / .webmanifest served as application/octet-stream (missing MIME entries). Trivial fix; only bites on vinext start (the CF deploy serves public files via ASSETS with correct MIME). area: static · upstream: unfiled · good first issue
• next.config headers() appends instead of overriding the default Cache-Control (duplicate header) #12 — next.config headers() duplicates Cache-Control / not applied to static assets. Fully covered (with tests) by fix(prod-server): apply next.config headers() to static assets (#1551) cloudflare/vinext#1658 — a stalled draft that just needs a rebase + un-draft nudge. area: static · upstream: has-PR
• vinext deploy --prerender-all fails: deploy build doesn't emit prerender secret/dist → 'No build output found in dist' #17 — vinext deploy --prerender-all fails ("No build output found in dist"). Part of the deploy cluster; related prerender bug Pages Router prerender: pages under /api-... and lazy catchall pages never finish loading cloudflare/vinext#1542. area: deploy · upstream: roadmap

🟢 P3 — Low / app-owned

• vinext deploy with a custom vite.config fails on missing cloudflare() (and the local-vs-deploy wrangler.jsonc story) #14 — vinext deploy errors on missing cloudflare() with a custom vite.config (+ the local-vs-deploy wrangler.jsonc story). The cloudflare()-lifecycle friction behind the argv-sniff hack; note vinext deploy is now deprecated in favor of @vinext/cloudflare deploy. area: deploy · upstream: unfiled
• Cloudflare dashboard deploy: split build + wrangler deploy conflicts with vinext — must skip build and use vinext deploy #2 — Cloudflare dashboard deploy: split build + wrangler deploy conflicts — must skip the build step and use vinext deploy. Mostly a deploy-workflow note. area: deploy · documentation
• next.config webpack block silently dropped → in-browser ESLint linter breaks (assert stub, esquery ESM, rule bloat) #7 — next.config webpack block dropped → in-browser ESLint breaks (assert stub, esquery ESM, rule bloat). Mostly app-owned: providing your own Vite polyfills is the expected workflow, and IgnorePlugin/raf/process are webpack plugins vinext intentionally skips. One narrow slice is worth filing: probeWebpackConfig discards already-recovered resolve.alias when the webpack() fn later throws (e.g. require('webpack') on a Vite project). area: config · upstream: app-owned

---

Clusters (same root cause, different symptom)

• Dev broken: Tracking: vinext dev is unusable for this app — every route 404s (workerd/no-fs) or 500s (dev module-runner can't CJS-interop the per-request MDX compile chain) #16 (umbrella) ← vinext dev SSR module-runner doesn't CJS-interop UMD/CJS deps (classnames window, parse-numeric-range exports) #6 (fixable root, fix: support CommonJS node_modules in Pages Router dev cloudflare/vinext#665). Upstream: SSR dev server fails with "module is not defined" for CJS dependencies (void-elements, highlight.js, etc.) cloudflare/vinext#585, Pages Router: _next/data JSON endpoint not implemented cloudflare/vinext#1330.
• Deploy broken: Pages Router: getStaticProps runs per-request instead of prerendering → fs-backed SSG apps 500 on Cloudflare Workers (needs --prerender-all) #15 (root: fs read at request time) ← vinext deploy --prerender-all fails: deploy build doesn't emit prerender secret/dist → 'No build output found in dist' #17 (prerender-all), vinext deploy with a custom vite.config fails on missing cloudflare() (and the local-vs-deploy wrangler.jsonc story) #14 (cloudflare() lifecycle), Cloudflare dashboard deploy: split build + wrangler deploy conflicts with vinext — must skip build and use vinext deploy #2 (dashboard workflow). Upstream trackers: Static pre-rendering at build time cloudflare/vinext#9, Populating remote cache during deployment cloudflare/vinext#562, Pages Router: getServerSideProps SSR returns 500 Internal Server Error cloudflare/vinext#1458, Pages Router: _next/data JSON endpoint not implemented cloudflare/vinext#1330, Pages Router prerender: pages under /api-... and lazy catchall pages never finish loading cloudflare/vinext#1542.

✅ Already fixed upstream & closed (reference)

Issue	Fixed by	Released
#3 optional catch-all root	cloudflare/vinext#2238	vinext 0.2.0
#5 JSX in .js optimizeDeps scanner	cloudflare/vinext#2434	next release
#8 next/image fixed-width srcSet	cloudflare/vinext#2310	vinext 0.2.0
#9 reactStrictMode not enforced	cloudflare/vinext#2433	next release
#13 .cjs config resolve.extensions	cloudflare/vinext#2435	next release

---

This index is maintained by hand; update it when issues are opened/closed or change priority.