Wrangler Changelog
 2024-08-06
 3.69.1
- #6432 cba2e25Thanks @petebacondarwin! - fix: prevent crash when running wrangler dev due to missing dependency
 3.69.0
- #6392 - c3e19b7Thanks @taylorlee! - feat: log Worker startup time in the- version uploadcommand
- #6370 - 8a3c6c0Thanks @CarmenPopoviciu! - feat: Create very basic Asset Server Worker and plumb it into- wrangler dev- These changes do the ground work needed in order to add Assets support for Workers in - wrangler dev. They implement the following:- it creates a new package called workers-sharedthat hosts theAsset Server Worker, and theRouter Workerin the future
- it scaffolds the Asset Server Workerin some very basic form, with basic configuration. Further behaviour implementation will follow in a subsequent PR
- it does the ground work of plumbing ASW into Miniflare
 
- it creates a new package called 
- #6392 - c3e19b7Thanks @taylorlee! - fix: remove bundle size warning from Worker deploy commands- Bundle size was a proxy for startup time. Now that we have startup time reported, focus on bundle size is less relevant. 
 2024-08-01
 3.68.0
- #6318 - dc576c8Thanks @danlapid! - feat: Add a log for worker startup time in wrangler deploy
- #6097 - 64f34e8Thanks @RamIdeas! - feat: implements the- --experimental-dev-env(shorthand:- --x-dev-env) flag for- wrangler pages dev
- #6379 - 31aa15cThanks @RamIdeas! - fix: clearer error message when trying to use Workers Sites or Legacy Assets with- wrangler versions upload
- #6367 - 7588800Thanks @RamIdeas! - fix: implicitly cleanup (call- stop()) in- unstable_devif the returned Promise rejected and the- stop()function was not returned
- #6330 - cfbdedeThanks @RamIdeas! - fix: when the worker’s request.url is overridden using the- hostor- localUpstream, ensure- portis overridden/cleared too- When using - --localUpstream=example.com, the request.url would incorrectly be “example.com:8787” but is now “example.com”.- This only applies to - wrangler dev --x-dev-envand- unstable_dev({ experimental: { devEnv: true } }).
- #6365 - 13549c3Thanks @WalshyDev! - fix: WASM modules meant that- wrangler versions secret ...could not properly update the version. This has now been fixed.
 2024-07-26
 3.67.1
- #6312 - 67c611aThanks @emily-shen! - feat: add CLI flag and config key for experimental Workers + Assets- This change adds a new experimental CLI flag ( - --experimental-assets) and configuration key (- experimental_assets) for the new Workers + Assets work.- The new flag and configuration key are for the time being “inactive”, in the sense that no behaviour is attached to them yet. This will follow up in future work. 
- Updated dependencies [ - b3c3cb8]:
 2024-07-25
 3.67.0
- #4545 - e5afae0Thanks @G4brym! - Remove experimental/beta constellation commands and binding, please migrate to Workers AI, learn more here https://developers.cloudflare.com/workers-ai/. This is not deemed a major version bump for Wrangler since these commands were never generally available.
- #6322 - 373248eThanks @IRCody! - Add cloudchamber scope to existing scopes instead of replacing them.- When using any cloudchamber command the cloudchamber scope will now be added to the existing scopes instead of replacing them. 
- #6276 - a432a13Thanks @CarmenPopoviciu! - feat: Add support for- wrangler.jsonc- This commit adds support for - wrangler.jsoncconfig file for Workers. This feature is available behind the- --experimental-json-configflag (just like- wrangler.json).- To use the new configuration file, add a - wrangler.jsoncfile to your Worker project and run- wrangler dev --experimental-json-configor- wrangler deploy --experimental-json-config.- Please note that this work does NOT add - wrangler.jsonor- wrangler.jsoncsupport for Pages projects!
- #6168 - 1ee41ffThanks @IRCody! - feature: Add list and remove subcommands to cloudchamber registries command.
- #6331 - e6ada07Thanks @threepointone! - fix: only warn about miniflare feature support (ai, vectorize, cron) once- We have some warnings in local mode dev when trying to use ai bindings / vectorize / cron, but they are printed every time the worker is started. This PR changes the warning to only be printed once per worker start. 
 2024-07-23
 3.66.0
- #6295 - ebc85c3Thanks @andyjessop! - feat: introduce an experimental flag for- wrangler typesto dynamically generate runtime types according to the user’s project configuration.
- #6272 - 084d39eThanks @emily-shen! - fix: add- legacy-assetsconfig and flag as alias of current- assetsbehavior- The existing behavior of the assetsconfig key/flag will change on August 15th.
- legacy-assetswill preserve current functionality.
 
- The existing behavior of the 
- #6203 - 5462eadThanks @geelen! - fix: Updating to match new D1 import/export API format
- #6315 - 3fd94e7Thanks @penalosa! - chore: Add RayID to- wrangler loginerror message displayed when a user hits a bot challenge page
 2024-07-19
 3.65.1
- #6267 - 957d668Thanks @WalshyDev! - chore: add total module size to the logged table, this makes it much easier to see the total size of all modules combined.
- #6244 - e7c06d7Thanks @gabivlj! - fix: wrangler cloudchamber json errors are properly formatted
- Updated dependencies [ - 779c713]:
 2024-07-16
 3.65.0
- #6194 - 25afcb2Thanks @zebp! - chore: Add duration and sourcemap size to upload metrics event- Wrangler will now send the duration and the total size of any sourcemaps uploaded with your Worker to Cloudflare if you have metrics enabled. 
- #6259 - eb201a3Thanks @ottomated! - chore: Add types to DurableObjectNamespace type generation. For example:interface Env {OBJECT: DurableObjectNamespace<import("./src/index").MyDurableObject>;}
- #6245 - e4abed3Thanks @OilyLime! - feature: Add support for Hyperdrive over Access configs
- #6255 - d497e1eThanks @rozenmd! - fix: teach wrangler init –from-dash about d1 bindings- This PR teaches - wrangler init --from-dashabout D1 bindings, so they aren’t incorrectly added to the wrangler.toml as unsafe bindings.
- #6258 - 4f524f2Thanks @dom96! - feature: Add warning about deploying Python with requirements.txt- This expands on the warning shown for all Python Workers to include a message about deploying Python Workers with a requirements.txt not being supported. 
- #6249 - 8bbd824Thanks @petebacondarwin! - chore: Update config-schema.json for the wrangler.toml
- #5955 - db11a0fThanks @harugon! - fix: correctly escape newlines in- constructTypefunction for multiline strings- This fix ensures that multiline strings are correctly handled by the - constructTypefunction. Newlines are now properly escaped to prevent invalid JavaScript code generation when using the- wrangler typescommand. This improves robustness and prevents errors related to multiline string handling in environment variables and other configuration settings.
- #6263 - fa1016cThanks @petebacondarwin! - fix: use cli script-name arg when deploying a worker with queue consumers
- Updated dependencies [ - 0d32448]:
 2024-07-11
 3.64.0
- #4925 - 7d4a4d0Thanks @dom96! - feature: whoami, logout and login commands mention the CLOUDFLARE_API_TOKEN env var now- It is easy to get confused when trying to logout while the CLOUDFLARE_API_TOKEN env var is set. The logout command normally prints out a message which states that the user is not logged in. This change rectifes this to explicitly call out that the CLOUDFLARE_API_TOKEN is set and requests that the user unsets it to logout. 
- #5032 - 75f7928Thanks @dbenCF! - Adding client side error handling for R2 when the user tries to create a bucket with an invalid name. The purpose of this addition is to provide the user with more context when encountering this error.
- #4398 - 4b1e5bcThanks @mattpocock! - fix: update tsconfig for Workers generated by wrangler init