-
Notifications
You must be signed in to change notification settings - Fork 732
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: --assets
/ config.assets
to serve a folder of static assets
#1237
Conversation
🦋 Changeset detectedLatest commit: d71d3f0 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
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 |
A wrangler prerelease is available for testing. You can install this latest build in your project with: npm install --save-dev https://prerelease-registry.developers.workers.dev/runs/2516392147/npm-package-wrangler-1237 You can reference the automatically updated head of this PR with: npm install --save-dev https://prerelease-registry.developers.workers.dev/prs/1237/npm-package-wrangler-1237 Or you can use npx https://prerelease-registry.developers.workers.dev/runs/2516392147/npm-package-wrangler-1237 dev path/to/script.js |
fbefa20
to
d9019b5
Compare
ca94b13
to
fef6023
Compare
--assets
/ config.assets
to serve a folder of static assets--assets
/ config.assets
to serve a folder of static assets
fef6023
to
8aa41bf
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is a huge step forward for assets! 🥳
I'm going add an experimental warning on this and land it |
8aa41bf
to
fdcb02f
Compare
This adds support for defining `assets` in `wrangler.toml`. You can configure it with a string path, or a `{bucket, include, exclude}` object (much like `[site]`). This also renames the `--experimental-public` arg as `--assets`. Via #1162
fdcb02f
to
d71d3f0
Compare
Hooray! 😀 |
This adds support for defining
assets
inwrangler.toml
. You can configure it with a string path, or a{bucket, include, exclude}
object (much like[site]
). This also renames the--experimental-public
arg as--assets
.Via #1162
Followup tasks (I'll make issues for each of these later, but logging here for visibility)
--assets
for service-worker Workers #1295){cacheControl: { browserTTL: number, edgeTTL: number, bypassCache: boolean }, singlePageApp: boolean }
_headers
--assets
/config.assets
is used (feat: entry point is not mandatory if--assets
is passed #1289)