Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Cloudflare deploy: framework prerender inside `void deploy`'s build deletes `.wrangler/deploy/config.json` (ENOENT)

Offen Anfängerfreundlich
  • Stimmt etwas nicht?
#463 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
2/5
Geschätzter Aufwand
1-3 Stunden
Anfängerfreundlichkeit
78/100
Issue-Typ
Bug
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
typescript
Bereich
build-system, cloud

Rechercherichtung

Beginne mit restorePreviewPointer in dist/index.mjs und vergleiche dessen Deploy-Build-Prüfung mit der im Issue beschriebenen Prüfung auf der Stash-Seite. Führe die bereitgestellte Reproduktion mit zwei Builds aus und überprüfe anschließend, dass .wrangler/deploy/config.json nach dem Build im Deploy-Modus bestehen bleibt, wenn ein Stash vorhanden ist, während sich das manuelle Preview-Verhalten nicht ändert.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Problem

In a TanStack Start app with voidPlugin() and TanStack's own build-time prerender (tanstackStart({ prerender: { enabled: true } })), void deploy fails after the build whenever an earlier plain vite build left a stashed pointer in .void/:

[prerender] Prerendered 4 pages:
...
◇ Preparing deployment...
■ ENOENT: no such file or directory, open '<root>/apps/web/.wrangler/deploy/config.json'

TanStack Start prerenders by starting a Vite preview server inside the build process. Void's plugin sees isPreview === true there and runs the preview restore path meant for a manual vite preview, including in the deploy build:

vite build              ── closeBundle: stash .wrangler/deploy/config.json → .void/preview-deploy-config.json
void deploy
  └ child build (VOID_CLOUDFLARE_DEPLOY_BUILD=1)
      ├ build writes a fresh .wrangler/deploy/config.json
      ├ prerender starts a Vite preview server
      │   └ config(): isPreview → restoreCloudflarePreviewPointer()
      │       ├ writes the stash from the earlier build over the pointer
      │       └ process.once("exit", rmSync(.wrangler/deploy/config.json))
      └ child exits → pointer deleted
  └ readGeneratedDeployConfig() → ENOENT

The stash side already skips deploy builds (closeBundle checks VOID_CLOUDFLARE_DEPLOY_BUILD !== "1"). The restore side has no such check (dist/index.mjs, restorePreviewPointer in voidPlugin).

This is the same pointer mechanism as #419, reached from the other direction. There a preview could not find the pointer. Here a preview inside a deploy build removes it.

Repro

A fresh clone reproduces it without void connect and without Cloudflare credentials. The deploy-mode build uses the env void deploy gives its build child.

git clone https://github.com/SweetRetry/void-starter && cd void-starter
git checkout 5230137
pnpm install
cd apps/web
pnpm exec vp build                                                  # plain build, stashes the pointer
VOID_CLOUDFLARE_DEPLOY_BUILD=1 NODE_ENV=production pnpm exec vp build   # what void deploy runs
ls .wrangler/deploy/config.json                                     # missing

Prerender is configured in apps/web/vite.config.ts. The repo's deploy script works around the bug by deleting .void/preview-deploy-config.json first, so call vp build directly as above.

Controls, each starting from an empty .wrangler/deploy and .void/preview-deploy-config.json:

Case Stash before deploy build Prerender Pointer after deploy build
A present on missing
B deleted on present
C present off present

An exit listener registered through NODE_OPTIONS=--require (so it runs before Void's) saw the pointer present in case A. The outer processes then saw it missing, so it is removed by the exit cleanup.

Suggested fix

Skip the restore in deploy builds, the same check the stash side already has:

 const restorePreviewPointer = () => {
   if (!existsSync(join(root, "void.config.ts"))) return;
+  if (process.env["VOID_CLOUDFLARE_DEPLOY_BUILD"] === "1") return;
   if (restoreCloudflarePreviewPointer(root) && !scheduledPreviewPointerCleanups.has(root)) {

With this patch applied to dist/index.mjs, case A keeps .wrangler/deploy/config.json ({"configPath":"../../dist/server/wrangler.json"}) after the deploy-mode build. A manual vite preview still finds the build output and gets as far as the remote binding session, which then fails only for lack of an API token in a non-interactive shell. That path runs without the env var, so its code is unchanged.

An alternative is for void deploy to remove .void/preview-deploy-config.json before it starts the build. That is the current workaround.

Question

The framework docs describe routing.prerender (deploy-time edge prerendering) for framework mode and don't mention a framework's own build-time prerender. Is TanStack Start's prerender option a supported setup with Void? We chose it so the blog pages ship as static assets in dist/client and a prerender failure fails the build.

Environment

  • void 1.1.11
  • @tanstack/react-start 1.169.2
  • @cloudflare/vite-plugin 1.64.0, wrangler 4.151.0
  • vite-plus 1.3.0
  • Node 24.14.1, pnpm 12.0.0, macOS
Vorherrschende Sprache
TypeScript
Sterne
402
Forks
32
Ø Merge
12 Std. 28 Min.
Gemergte PRs (30 T.)
77

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus voidzero-dev/void

Alle Issues in voidzero-dev/void

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.