Detect non-framework static sites

[penalosa]

Fixes https://jira.cfdata.org/browse/DEVX-2266

Support non-framework static sites with autoconfig by looking for a folder that contains an index.html file, and treating that as the output directory.

---

• Tests
  • Tests included
  • Tests not necessary because:
• Public documentation
  • Cloudflare docs PR(s):
  • Documentation not necessary because: pending
• Wrangler V3 Backport
  • Wrangler PR:
  • Not necessary because: new feature

[changeset-bot]

🦋 Changeset detected

Latest commit: 955c719

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[pkg-pr-new]

create-cloudflare

npm i https://pkg.pr.new/create-cloudflare@11180

@cloudflare/kv-asset-handler

npm i https://pkg.pr.new/@cloudflare/kv-asset-handler@11180

miniflare

npm i https://pkg.pr.new/miniflare@11180

@cloudflare/pages-shared

npm i https://pkg.pr.new/@cloudflare/pages-shared@11180

@cloudflare/unenv-preset

npm i https://pkg.pr.new/@cloudflare/unenv-preset@11180

@cloudflare/vite-plugin

npm i https://pkg.pr.new/@cloudflare/vite-plugin@11180

@cloudflare/vitest-pool-workers

npm i https://pkg.pr.new/@cloudflare/vitest-pool-workers@11180

@cloudflare/workers-editor-shared

npm i https://pkg.pr.new/@cloudflare/workers-editor-shared@11180

@cloudflare/workers-utils

npm i https://pkg.pr.new/@cloudflare/workers-utils@11180

wrangler

npm i https://pkg.pr.new/wrangler@11180

commit: 955c719

[github-actions]

Failed to automatically backport this PR's changes to Wrangler v3. Please manually create a PR targeting the v3-maintenance branch with your changes. Thank you for helping us keep Wrangler v3 supported!

Depending on your changes, running git rebase --onto v3-maintenance main penalosa/pure-static-autoconfig might be a good starting point.

Notes:

• your PR branch should be named v3-backport-11180
• add the skip-v3-pr label to the current PR to stop this workflow from failing

[dario-piotrowicz]

I think we are missing a test to make sure that we detect when a fist child dir is actually detected as the outputDir?

[penalosa]

I'm not sure what you mean here—could you expand?

[dario-piotrowicz]

oh sorry I misread the test below 🤔

I thought it was checking a directory of this shape:

• index.html
• random
  • index.html

and making sure that the html from the random dir wasn't being picked up

Sorry my bad 🙂

---

That being said, maybe the case I just described should also be tested?

e.g.

it("outputDir should prioritize the project directory over its child directories", async () => {
	await seed({
	    "index.html": `<h1>Hello World</h1>`,
		"public/index.html": `<h1>Hello World</h1>`,
	});

	await expect(details.getDetailsForAutoConfig()).resolves.toMatchObject({
		outputDir: process.cwd(),
	});
});

?

[Hafiz613]

در تاریخ چهارشنبه, نومبر ۵, ۲۰۲۵،‏ ۹:۱۳ ب.ظ Somhairle MacLeòid < ***@***.***> نوشت:

…

Merged #11180 <#11180> into main. — Reply to this email directly, view it on GitHub <#11180 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BSNJN5HKW4H5HVCRKM5S5WT33ISLDAVCNFSM6AAAAACLG3LHRSVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMRQG4ZTKNZRG4YTMMA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>