Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

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

Open Beginner friendly
  • Is something wrong?
#463 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
build-system, cloud

Research direction

Start with restorePreviewPointer in dist/index.mjs and compare its deploy-build guard with the stash-side check described in the issue. Run the provided two-build reproduction, then verify that .wrangler/deploy/config.json remains after the deploy-mode build when a stash is present, while manual preview behavior remains unchanged.

Written by the indexing model from the issue text.

Description

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
Dominant language
TypeScript
Stars
402
Forks
32
Avg merge
12h 28m
Merged PRs (30d)
77

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from voidzero-dev/void

All issues in voidzero-dev/void

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.