Minor Changes
-
#7476
5124b5d
Thanks @WalshyDev! - feat: allow routing to Workers with Assets on any HTTP route, not just the root. For example,example.com/blog/*
can now be used to serve assets.
These assets will be served as though the assets directly were mounted to the root.
For example, if you haveassets = { directory = "./public/" }
, a route like"example.com/blog/*"
and a file./public/blog/logo.png
, this will be available atexample.com/blog/logo.png
. Assets outside of directories which match the configured HTTP routes can still be accessed with the Assets binding or with a Service binding to this Worker. -
#7380
72935f9
Thanks @CarmenPopoviciu! - Add Workers + Assets support inwrangler dev --remote
Patch Changes
-
#7573
fb819f9
Thanks @emily-shen! - feat: add experimental_readRawConfig()Adds a Wrangler API to find and read a config file
-
#7549
42b9429
Thanks @penalosa! - Expand metrics collection to:- Detect Pages & Workers CI
- Filter out default args (e.g.
--x-versions
,--x-dev-env
, and--latest
) by only including args that were inargv
-
#7583
8def8c9
Thanks @penalosa! - Revert support for custom unenv resolve path to address an issue with Wrangler failing to deploy Pages projects withnodejs_compat_v2
in some cases