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

Static Cloudflare deploy ignores `cloudflare.assets.html_handling`

Closed Beginner friendly
  • Is something wrong?
#580 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@0froq is already working on this.

Since Oct 25, 2026.

  • #3 by @0froq — open
  • #588 by @0froq — merged

Assessment

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

Research direction

Start with packages/deploy-cloudflare/src/static.ts near line 114, then trace how assetConfig is built in packages/void/src/cli/deploy-cloudflare-static.ts and packages/void/src/cli/package.ts. Check how static deploy config chooses html_handling when the root Cloudflare setting is present or absent; done when the authored value is retained and the fallback remains auto-trailing-slash.

Written by the indexing model from the issue text.

Description

With inference.appType: "static" and void deploy --platform cloudflare, the deployed Worker always gets html_handling: "auto-trailing-slash", whatever void.config.ts sets:

export default defineConfig({
  cloudflare: { assets: { html_handling: "drop-trailing-slash" } },
  inference: { appType: "static", outputDir: "dist/client" },
});

Framework deploys honor this setting; static deploys drop it.

Cause:

Effect: a prerendered site that writes about/index.html and links to /about gets a 307 to /about/ on every full page load, and there's no config to stop it.

Expected: use the authored cloudflare.assets.html_handling when set, and fall back to auto-trailing-slash only when it isn't.

Workaround: write pages as about.html instead of about/index.html. In TanStack Start that's prerender.autoSubfolderIndex: false.

void 1.2.1, @void/deploy-cloudflare 1.2.1.

Dominant language
TypeScript
Stars
580
Forks
56
Avg merge
11h 32m
Merged PRs (30d)
158

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.