feat(cloudflare): cacheControl
support for public assets with with maxAge
#922
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
π Linked issue
#919
β Type of change
π Description
For now if you serve website to Cloudflare Workers you exceed free (and even paid) limits very fast because each request serves assets directly from worker and never cache in browser.
I think that it will be great to get
maxAge
from publicAssetURLOptions, but i didn't touch rollup virtual code to make it work.π Checklist