Document new emitClientAsset function

[matthewp]

Description (required)

emitClientAsset is a new function exported from astro/assets/utils that's useful for integration authors that want to emit an asset that should be available in the client asset folder (such as images).

Related issues & labels (optional)

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

[netlify]

✅ Deploy Preview for astro-docs-2 ready!

Name	Link
🔨 Latest commit	8bf1c76
🔍 Latest deploy log	https://app.netlify.com/projects/astro-docs-2/deploys/698a246fee1b8800075fdea4
😎 Deploy Preview	https://deploy-preview-13223--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.
en/reference/modules/astro-assets.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]

Thanks for this, @matthewp !

(Will also tag in @ArmandPhilippot since I'm not sure whether it would be helpful to link out to the Rollup.* types? e.g. we show an example with type, name, and source, but not how someone is supposed to know what values they can use there.)

Just tried to edit the text to match our style a little more, but will need your help for some clarity on exactly what's happening and what (might be?) an implementation detail to know for sure!

Also, as mentioned in the Astro PR, the Cloudflare breaking change will need an entry on the Cloudflare adapter's own page since we've got a separate, specific upgrade guide for the Cloudflare major. That can be in this PR if you prefer, or a separate one! https://v6.docs.astro.build/en/guides/integrations-guide/cloudflare/#upgrading-to-v13-and-astro-6

[ArmandPhilippot]

I left a suggestion to handle Sarah's comment re: "I'm not sure whether it would be helpful to link out to the Rollup.* types?". When we have docs, I think this is helpful to add a link but unfortunately that's not always the case.

And two more suggestions:

• I think a link to Rollup in another place could be helpful
• I'm not sure what this is in the code snippet and we might need to add more context here (either in the code snippet or as a sentence to introduce it and explain what this is).