feat(cloudflare): support vite plugins options

[florian-lefebvre]

Description (required)

Related issues & labels (optional)

• Closes #
• Suggested label:

For Astro version: 6.x. See astro PR #15556.

[netlify]

✅ Deploy Preview for astro-docs-2 ready!

Name	Link
🔨 Latest commit	44cc32d
🔍 Latest deploy log	https://app.netlify.com/projects/astro-docs-2/deploys/699dd5c2724fb30008ef57cd
😎 Deploy Preview	https://deploy-preview-13278--astro-docs-2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[astrobot-houston]

Lunaria Status Overview

🌕 This pull request will trigger status changes.

Learn more

By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.

You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

File	Note
en/guides/integrations-guide/cloudflare.mdx	Source changed, localizations will be marked as outdated.

Warnings reference

Icon	Description
🔄️	The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

[sarah11918]

I'm going to guess that this link is the best one we have? On that page it says absolutely nothing about these options, but I also couldn't easily find anywhere these 6 options were all mentioned together. (The first 4 are mentioned on the specific API page - https://developers.cloudflare.com/workers/vite-plugin/reference/api/ but the last two are not)

[florian-lefebvre]

Yeah maybe we could link to https://developers.cloudflare.com/workers/vite-plugin/reference/api/#interface-pluginconfig but otherwise, I also failed to find docs for the rest

[sarah11918]

I'll let you make the call! The API reference page is maybe marginally more helpful in our immediate context of saying you can set these options? But the above link is the "entry page" to everything about the plugin itself, which is a perfectly reasonable thing to link to when mentioning it for the first time! If there were a more obvious link, we'd use it. Right now, I don't think there's a clear winner, so go with your gut!

[florian-lefebvre]

@sarah11918 can I get your review on the associated changeset?