NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm, #4709 most downloaded on npm
Command-line interface for all things Cloudflare Workers
Latest stable
4.163.0
Last release today
16 Nov 2026
Ships on a steady schedule
a new release about every 8 days
Nearly every release is documented
notes for 60 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
14 years old
4977 releases · first in 2012
Drag across the ruler to compare, or tap a release to open it.
both hyperdrive create and hyperdrive update now support updating configs with connection strings.
#6999 0111edb Thanks @garvit-gupta! - docs: Vectorize GA Announcement Banner
#6916 a33a133 Thanks @garrettgu10! - Local development now supports Vectorize bindings
#7004 15ef013 Thanks @garvit-gupta! - feat: Enable Vectorize query by id via Wrangler
#7092 038fdd9 Thanks @jonesphillip! - Added location hint option for the Wrangler R2 bucket create command
#7024 bd66d51 Thanks @xortive! - feature: allow using a connection string when updating hyperdrive configs
both hyperdrive create and hyperdrive update now support updating configs with connection strings.
#7091 68a2a84 Thanks @taylorlee! - fix: synchronize observability settings during wrangler versions deploy
When running wrangler versions deploy, Wrangler will now update observability settings in addition to logpush and tail_consumers. Unlike wrangler deploy, it will not disable observability when observability is undefined in wrangler.toml.
#7080 924ec18 Thanks @vicb! - chore(wrangler): update unenv dependency version
#7097 8ca4b32 Thanks @emily-shen! - fix: remove deprecation warnings for wrangler init
We will not be removing wrangler init (it just delegates to create-cloudflare now). These warnings were causing confusion for users as it wrangler init is still recommended in many places.
#7073 656a444 Thanks @penalosa! - Internal refactor to remove es-module-lexer and support wrangler types for Workers with Durable Objects & JSX
#7024 bd66d51 Thanks @xortive! - fix: make individual parameters work for wrangler hyperdrive create when not using HoA
wrangler hyperdrive create individual parameters were not setting the database name correctly when calling the api.
#7024 bd66d51 Thanks @xortive! - refactor: use same param parsing code for wrangler hyperdrive create and wrangler hyperdrive update
ensures that going forward, both commands support the same features and have the same names for config flags
Your coding agent can read these notes before it upgrades. Set up the MCP server →
This also adds an id option to allow users to optionally customize the new instance id.
1de309b Thanks @jkoe-cf! - feature: allowing users to specify a description when creating an event notification rule#7011 cef32c8 Thanks @GregBrimble! - fix: Correctly apply Durable Object migrations for namespaced scripts
#7067 4aa35c5 Thanks @LuisDuarte1! - Change trigger command to comply with the current workflows endpoint.
This also adds an id option to allow users to optionally customize the new instance id.
#7082 3f1d79c Thanks @LuisDuarte1! - Change to new terminate instance workflow endpoint
#7036 e7ea600 Thanks @penalosa! - Reduce KV bulk upload bucket size to 1000 (from the previous 5000)
#7068 a2afcf1 Thanks @RamIdeas! - log warning of Workflows open-beta status when running deploying a Worker that contains a Workflow binding
#7065 b219296 Thanks @penalosa! - Internal refactor to remove React/ink from all non-wrangler dev flows
#7064 a90980c Thanks @penalosa! - Fix wrangler dev --remote --show-interactive-dev-session=false by only enabling hotkeys after account selection if hotkeys were previously enabled
#7045 5ef6231 Thanks @RamIdeas! - Add preliminary support for Workflows in wrangler dev
#7075 80e5bc6 Thanks @LuisDuarte1! - Fix params serialization when send the trigger workflow API
Previously, wrangler did not parse the params sending it as a string to workflow's services.
Updated dependencies [760e43f, 8dc2b7d, 5ef6231]:
To bind to a workflow, add a workflows section in your wrangler.toml:
6b97353 Thanks @bthwaites! - Add jurisdiction option to R2 event notification wrangler actions#5737 9bf51d6 Thanks @penalosa! - Validate duplicate bindings across all binding types
#7010 1f6ff8b Thanks @vicb! - chore: update unenv dependency version
#7012 244aa57 Thanks @RamIdeas! - Add support for Workflow bindings (in deployments, not yet in local dev)
To bind to a workflow, add a workflows section in your wrangler.toml:
[[workflows]]
binding = "WORKFLOW"
name = "my-workflow"
class_name = "MyDemoWorkflow"
and export an entrypoint (e.g. MyDemoWorkflow) in your script:
import { WorkflowEntrypoint } from "cloudflare:workers";
export class MyDemoWorkflow extends WorkflowEntrypoint<Env, Params> {...}
#7039 e44f496 Thanks @penalosa! - Only show dev registry connection status in local dev
#7037 e1b93dc Thanks @emily-shen! - fix: ask for confirmation before creating a new Worker when uploading secrets
Previously, wrangler secret put KEY --name non-existent-worker would automatically create a new Worker with the name non-existent-worker. This fix asks for confirmation before doing so (if running in an interactive context). Behaviour in non-interactive/CI contexts should be unchanged.
#7015 48152d6 Thanks @RamIdeas! - add wrangler workflows ... commands
#7041 045787b Thanks @CarmenPopoviciu! - Show wrangler pages dev --proxy warning
On Node.js 17+, wrangler will default to fetching only the IPv6 address. With these changes we warn users that the process listening on the port specified via --proxy should be configured for IPv6.
#7018 127615a Thanks @emily-shen! - fix: log successful runs of d1 execute in local
#6970 a8ca700 Thanks @oliy! - Add HTTP authentication options for Workers Pipelines
#7005 6131ef5 Thanks @edmundhung! - fix: prevent users from passing multiple arguments to non array options
#7046 f9d5fdb Thanks @oliy! - Minor change to 3rd party API shape for Workers Pipelines
#6972 c794935 Thanks @penalosa! - Add (local) indicator to bindings using local data
Updated dependencies [809193e]:
This was a regression in the --x-dev-env flow recently turned on by default.
586c253 Thanks @courtney-sims! - feat: Adds new detailed pages deployment output type#6963 a5ac45d Thanks @RamIdeas! - fix: make wrangler dev --remote respect wrangler.toml's account_id property.
This was a regression in the --x-dev-env flow recently turned on by default.
#6996 b8ab809 Thanks @emily-shen! - fix: improve error messaging when accidentally using Workers commands in Pages project
If we detect a Workers command used with a Pages project (i.e. wrangler.toml contains pages_output_build_dir), error with Pages version of command rather than "missing entry-point" etc.
Updated dependencies [`5761020`, `7859a04`]:
Updated dependencies [`c863183`, `fd43068`]:
#6937 51aedd4 Thanks @lrapoport-cf! - fix: show help when kv commands are run without parameters
Updated dependencies [c863183, fd43068]:
Pulls in feat(node/net): implement Server mock.
#6927 2af75ed Thanks @emily-shen! - fix: respect CLOUDFLARE_ACCOUNT_ID with wrangler pages project commands
Fixes #4947
#6894 eaf71b8 Thanks @petebacondarwin! - fix: improve the rendering of build errors when bundling
#6920 2e64968 Thanks @vicb! - chore: update unenv dependency version
Pulls in feat(node/net): implement Server mock.
#6932 4c6aad0 Thanks @vicb! - fix: allow requireing unenv aliased packages
Before this PR requireing packages aliased in unenv would fail.
That's because require would load the mjs file.
This PR adds wraps the mjs file in a virtual ES module to allow requireing it.
### Patch Changes - #6923 `1320f20` Thanks @andyjessop! - chore: adds eslint-disable for ESLint error on empty typescript interface in workers-configu
1320f20 Thanks @andyjessop! - chore: adds eslint-disable for ESLint error on empty typescript interface in workers-configuration.d.tsFixes #5768 - issue with vitest and Pages projects with wrangler.toml
#6908 d696850 Thanks @penalosa! - fix: debounce restarting worker on assets dir file changes when --x-dev-env is enabled.
#6902 dc92af2 Thanks @threepointone! - fix: enable esbuild's keepNames: true to set .name on functions/classes
#6909 82180a7 Thanks @penalosa! - fix: Various fixes for logging in --x-dev-env, primarily to ensure the hotkeys don't wipe useful output and are cleaned up correctly
#6903 54924a4 Thanks @petebacondarwin! - fix: ensure that alias config gets passed through to the bundler when using new --x-dev-env
Fixes #6898
#6911 30b7328 Thanks @emily-shen! - fix: infer experimentalJsonConfig from file extension
Fixes #5768 - issue with vitest and Pages projects with wrangler.toml
Updated dependencies [5c50949]:
If you experience any issues, you can disable the flag with --x-dev-env=false. Please also let us know by opening an issue at https://github.com/cloud
#6408 3fa846e Thanks @RamIdeas! - feat: update the --experimental-dev-env (shorthand: --x-dev-env) flag to on-by-default
If you experience any issues, you can disable the flag with --x-dev-env=false. Please also let us know by opening an issue at https://github.com/cloudflare/workers-sdk/issues/new/choose.
#6854 04a8fed Thanks @penalosa! - chore: Include serialised FormData in debug logs
#6879 b27d8cb Thanks @petebacondarwin! - fix: the docs command should not crash if given search terms
Fixes a regression accidentally introduced by #3735.
#6873 b123f43 Thanks @zwily! - fix: reduce logging noise during wrangler dev with static assets
Updates to static assets are accessible by passing in --log-level="debug" but otherwise hidden.
#6881 7ca37bc Thanks @RamIdeas! - fix: custom builds outputting files in assets watched directory no longer cause the custom build to run again in an infinite loop
#6872 b2d094e Thanks @petebacondarwin! - fix: render a helpful build error if a Service Worker mode Worker has imports
A common mistake is to forget to export from the entry-point of a Worker, which causes Wrangler to infer that we are in "Service Worker" mode.
In this mode, imports to external modules are not allowed.
Currently this only fails at runtime, because our esbuild step converts these imports to an internal __require() call that throws an error.
The error message is misleading and does not help the user identify the cause of the problem.
This is particularly tricky where the external imports are added by a library or our own node.js polyfills.
Fixes #6648
#6792 27e8385 Thanks @penalosa! - fix: Handle more module declaration cases
#6838 7dbd0c8 Thanks @GregBrimble! - fix: Improve static asset upload messaging
### Minor Changes - #6801 `6009bb4` Thanks @RamIdeas! - feat: implement retries within wrangler deploy and wrangler versions upload to workaround spot
### Patch Changes - #6840 `5bfb75d` Thanks @a-robinson! - chore: update warning in wrangler dev --remote when using Queues to not mention beta status
5bfb75d Thanks @a-robinson! - chore: update warning in wrangler dev --remote when using Queues to not mention beta status### Patch Changes - #6819 `7ede181` Thanks @CarmenPopoviciu! - fix: Validate [routes] on configuration file changes
7ede181 Thanks @CarmenPopoviciu! - fix: Validate [routes] on configuration file changesUpdated dependencies [`5e2e62c`, `1c58a74`]:
#6824 1c58a74 Thanks @petebacondarwin! - fix: tidy up error messaging for unexpected use of Node.js APIs
Fixes #6822
Updated dependencies [5e2e62c, 1c58a74]:
### Patch Changes - #6753 `4e33f2c` Thanks @bluwy! - refactor: prevent bundling entire package.json in built code - #6812 `f700d37` Thanks @CarmenPopo
#6753 4e33f2c Thanks @bluwy! - refactor: prevent bundling entire package.json in built code
#6812 f700d37 Thanks @CarmenPopoviciu! - fix: Validate additional config properties for [observability]
#6751 638a550 Thanks @bluwy! - refactor: simplify date calculation and remove date-fns dependency
#6809 28cb0d7 Thanks @smellercf! - fix: Remove Beta tag from r2 event notification wrangler command descriptions
#6802 17eb8a9 Thanks @CarmenPopoviciu! - chore: rename experimental_assets to assets
#6781 0792fa0 Thanks @mikenomitch! - chore: tweaks warning when using node_compat
Some characters like [ ] @ are encoded by encodeURIComponent() but are often requested at an unencoded URL path. This change will make assets with fil
#6791 74d719f Thanks @penalosa! - fix: Add missing binding to init --from-dash
#6728 1ca313f Thanks @emily-shen! - fix: remove filepath encoding on asset upload and handle sometimes-encoded characters
Some characters like [ ] @ are encoded by encodeURIComponent() but are often requested at an unencoded URL path. This change will make assets with filenames with these characters accessible at both the encoded and unencoded paths, but to use the encoded path as the canonical one, and to redirect requests to the canonical path if necessary.
#6798 7d7f19a Thanks @emily-shen! - fix: error if an asset binding is provided without a Worker script
Updated dependencies [1ca313f]:
This commit fixes the current behaviour of watch mode for Workers with assets, and adds support for switching between static and dynamic Workers withi
#6775 ecd82e8 Thanks @CarmenPopoviciu! - fix: Support switching between static and dynamic Workers
This commit fixes the current behaviour of watch mode for Workers with assets, and adds support for switching between static and dynamic Workers within a single wrangler dev session.
#6762 2840b9f Thanks @petebacondarwin! - fix: error if a user inadvertently uploads a Pages _workers.js file or directory as an asset
#6778 61dd93a Thanks @CarmenPopoviciu! - fix: Error if Workers + Assets are run in remote mode
Workers + Assets are currently supported only in local mode. We should throw an error if users attempt to use Workers with assets in remote mode.
#6782 7655505 Thanks @vicb! - chore: update unenv dependency version
#6777 9649dbc Thanks @penalosa! - chore: Update CI messaging
#6779 3e75612 Thanks @emily-shen! - fix: include asset binding in wrangler types
Adds support for non-default build conditions and platform via the WRANGLER_BUILD_CONDITIONS and WRANGLER_BUILD_PLATFORM flags.
#6743 b45e326 Thanks @petebacondarwin! - fix: ability to build tricky Node.js compat scenario Workers
Adds support for non-default build conditions and platform via the WRANGLER_BUILD_CONDITIONS and WRANGLER_BUILD_PLATFORM flags.
Fixes https://github.com/cloudflare/workers-sdk/issues/6742
#6776 02de103 Thanks @zebp! - fix: disable observability on deploy if not explicitly defined in config
When deploying a Worker that has observability enabled in the deployed version but not specified in the wrangler.toml Wrangler will now set observability to disabled for the new version to match the wrangler.toml as the source of truth.
Updated dependencies [2ddbb65]:
Tail Workers are currently not supported for Workers with assets. This commit ensures we throw a corresponding error if users are attempting to config
#6744 e3136f9 Thanks @petebacondarwin! - chore: update unenv dependency version
#6749 9a06f88 Thanks @CarmenPopoviciu! - fix: Throw error when attempting to configure Workers with assets and tail consumers
Tail Workers are currently not supported for Workers with assets. This commit ensures we throw a corresponding error if users are attempting to configure tail_consumers via their configuration file, for a Worker with assets. This validation is applied for all wrangler dev, wrangler deploy, wrangler versions upload.
#6746 0deb42b Thanks @GregBrimble! - fix: Fix assets upload message to correctly report number of uploaded assets
#6745 6dbbb88 Thanks @jonesphillip! - fix: r2 bucket notification get <bucket_name> has been marked deprecated in favor of r2 bucket notification list <bucket_name> to reflect behavior.
Updated dependencies [2407c41]:
### Patch Changes - #6706 `1c42466` Thanks @jkoe-cf! - fix: making explicit to only send a body if there are rule ids specified in the config delete -
#6706 1c42466 Thanks @jkoe-cf! - fix: making explicit to only send a body if there are rule ids specified in the config delete
#6714 62082aa Thanks @OilyLime! - fix: rough edges when creating and updating Hyperdrive over Access configs
#6705 ea60a52 Thanks @emily-shen! - fix: include compatibility date in static-asset only uploads (experimental feature)
Updated dependencies [`5b5dd95`]:
Updated dependencies [`7a8bb17`]:
7a8bb17]:
Updated dependencies [`31bfd37`, `5d8547e`]:
When set, this will ensure that wrangler deploy and wrangler versions upload only deploy to Workers which match the provided tag.
#6643 f30c61f Thanks @WalshyDev! - feat: add "Deployment alias URL" to wrangler pages deploy if an alias is available for this deployment.
#6415 b27b741 Thanks @irvinebroque! - chore: Redirect wrangler generate [template name] and wrangler init to npm create cloudflare
#6647 d68e8c9 Thanks @joshthoward! - feat: Configure SQLite backed Durable Objects in local dev
#6696 0a9e90a Thanks @penalosa! - feat: Support WRANGLER_CI_MATCH_TAG environment variable.
When set, this will ensure that wrangler deploy and wrangler versions upload only deploy to Workers which match the provided tag.
#6702 aa603ab Thanks @hhoughgg! - feat: Hide wrangler pipelines until release
#6699 2507304 Thanks @joshthoward! - fix: Bugs when warning users using SQLite in Durable Objects in remote dev
#6693 0737e0f Thanks @GregBrimble! - fix: Persist Workers Assets when doing wrangler versions secrets put/bulk
Updated dependencies [d68e8c9, fed1fda]:
[[pipelines]] binding = "MY_PIPELINE" pipeline = "my-pipeline"
#6674 831f892 Thanks @andyjessop! - feat: Added new [[pipelines]] bindings. This creates a new binding that allows sending events to
the specified pipeline.
Example:
[[pipelines]] binding = "MY_PIPELINE" pipeline = "my-pipeline"
#6668 88c40be Thanks @zebp! - feature: add observability setting to wrangler.toml
Adds the observability setting which provides your Worker with automatic persistent logs that can be searched, filtered, and queried directly from the Workers dashboard.
#6679 2174127 Thanks @jkoe-cf! - feat: adding option to specify a rule within the config to delete (if no rules are specified, all rules get deleted)
#6666 4107f57 Thanks @threepointone! - feat: support analytics engine in local/remote dev
This adds "support" for analytics engine datasets for wrangler dev. Specifically, it simply mocks the AE bindings so that they exist while developing (and don't throw when accessed).
This does NOT add support in Pages, though we very well could do so in a similar way in a followup.
#6640 8527675 Thanks @petebacondarwin! - feat: experimental workers assets can be ignored by adding a .assetsignore file
This file can be added to the root of the assets directory that is to be uploaded alongside the Worker
when using experimental_assets.
The file follows the .gitignore syntax, and any matching paths will not be included in the upload.
#6652 648cfdd Thanks @bthwaites! - feat: Update R2 Get Event Notification response, display, and actions
#6625 8dcd456 Thanks @maxwellpeterson! - feature: Add support for placement hints
Adds the hint field to smart placement configuration. When set, placement hints will be used to decide where smart-placement-enabled Workers are run.
#6631 59a0072 Thanks @emily-shen! - feat: Add config options 'html_handling' and 'not_found_handling' to experimental_asset field in wrangler.toml
#6621 6523db2 Thanks @emily-shen! - fix: Validate routes in wrangler dev and wrangler deploy for Workers with assets
We want wrangler to error if users are trying to deploy a Worker with assets, and routes with a path component.
All Workers with assets must have either:
#6687 7bbed63 Thanks @GregBrimble! - fix: Fix asset upload count messaging
#6628 33cc0ec Thanks @GregBrimble! - chore: Improves messaging when uploading assets
#6671 48eeff4 Thanks @jkoe-cf! - fix: Update R2 Create Event Notification response
#6618 67711c2 Thanks @GregBrimble! - fix: Switch to multipart/form-data upload format for Workers Assets
This has proven to be much more reliable.
Updated dependencies [3f5b934, 59a0072]:
Adds a cloudchamber curl command which allows easy access to arbitrary cloudchamber API endpoints.
#6126 18c105b Thanks @IRCody! - feature: Add 'cloudchamber curl' command
Adds a cloudchamber curl command which allows easy access to arbitrary cloudchamber API endpoints.
#6649 46a91e7 Thanks @andyjessop! - feature: Integrate the Cloudflare Pipelines product into wrangler.
Cloudflare Pipelines is a product that handles the ingest of event streams into R2. This feature integrates various forms of managing pipelines.
Usage:
wrangler pipelines create <pipeline>: Create a new pipeline
wrangler pipelines list: List current pipelines
wrangler pipelines show <pipeline>: Show a pipeline configuration
wrangler pipelines update <pipeline>: Update a pipeline
wrangler pipelines delete <pipeline>: Delete a pipeline
Examples: wrangler pipelines create my-pipeline --r2 MY_BUCKET --access-key-id "my-key" --secret-access-key "my-secret" wrangler pipelines show my-pipeline wrangler pipelines delete my-pipline
#6612 6471090 Thanks @dario-piotrowicz! - fix: Add hyperdrive binding support in getPlatformProxy
example:
# wrangler.toml
[[hyperdrive]]
binding = "MY_HYPERDRIVE"
id = "000000000000000000000000000000000"
localConnectionString = "postgres://user:pass@127.0.0.1:1234/db"
// index.mjs
import postgres from "postgres";
import { getPlatformProxy } from "wrangler";
const { env, dispose } = await getPlatformProxy();
try {
const sql = postgres(
// Note: connectionString points to `postgres://user:pass@127.0.0.1:1234/db` not to the actual hyperdrive
// connection string, for more details see the explanation below
env.MY_HYPERDRIVE.connectionString
);
const results = await sql`SELECT * FROM pg_tables`;
await sql.end();
} catch (e) {
console.error(e);
}
await dispose();
Note: the returned binding values are no-op/passthrough that can be used inside node.js, meaning
that besides direct connections via the connect methods, all the other values point to the
same db connection specified in the user configuration
#6620 ecdfabe Thanks @petebacondarwin! - fix: don't warn about node:async_hooks if nodejs_als is set
Fixes #6011
Updated dependencies [5936282, 6471090]:
The version upload API returns a field indicating whether a preview exists for that version. If a preview exists and workers.dev is enabled, wrangler
#6603 a197460 Thanks @taylorlee! - feature: log version preview url when previews exist
The version upload API returns a field indicating whether a preview exists for that version. If a preview exists and workers.dev is enabled, wrangler will now log the full URL on version upload.
This does not impact wrangler deploy, which only prints the workers.dev route of the latest deployment.
#6550 8d1d464 Thanks @Pedr0Rocha! - feature: add RateLimit type generation to the ratelimit unsafe binding.
#6615 21a09e0 Thanks @RamIdeas! - chore: avoid potential double-install of create-cloudflare
When wrangler init delegates to C3, it did so via npm create cloudflare@2.5.0. C3's v2.5.0 was the first to include auto-update support to avoid npx's potentially stale cache. But this also guaranteed a double install for users who do not have 2.5.0 cached. Now, wrangler delegates via npm create cloudflare@^2.5.0 which should use the latest version cached on the user's system or install and use the latest v2.x.x.
#6603 a197460 Thanks @taylorlee! - chore: fix version upload log order
Previously deploy prints: upload timings deploy timings current version id
while version upload prints: worker version id upload timings
This change makes version upload more similar to deploy by printing version id after upload, which also makes more sense, as version ID can only be known after upload has finished.
Updated dependencies [`e8975a9`]:
dff8d44 Thanks @CarmenPopoviciu! - feat: add support for experimental assets in wrangler dev watch mode#6605 c4f0d9e Thanks @WalshyDev! - fix: ensure we update non-versioned Worker settings for the new deploy path in wrangler deploy
Updated dependencies [e8975a9]:
A few of the commands had an output that wasn't guarded by --x-versions those have been updated to use the newer output, we have tried to keep compati
#6571 a7e1bfe Thanks @penalosa! - feat: Add deployment http targets to wrangler deploy logs, and add url to pages deploy logs
#6497 3bd833c Thanks @WalshyDev! - chore: move wrangler versions ..., wrangler deployments ..., wrangler rollback and wrangler triggers ... out of experimental and open beta.
These are now available to use without the --x-versions flag, you can continue to pass this however without issue to keep compatibility with all the usage today.
A few of the commands had an output that wasn't guarded by --x-versions those have been updated to use the newer output, we have tried to keep compatibility where possible (for example: wrangler rollback will continue to output "Worker Version ID:" so users can continue to grab the ID).
If you wish to use the old versions of the commands you can pass the --no-x-versions flag. Note, these will be removed in the future so please work on migrating.
#6586 72ea742 Thanks @penalosa! - feat: Inject a 404 response for browser requested favicon.ico files when loading the /__scheduled page for scheduled-only Workers
#6497 3bd833c Thanks @WalshyDev! - feat: update wrangler deploy to use the new versions and deployments API.
This should have zero user-facing impact but sets up the most used command to deploy Workers to use the new recommended APIs and move away from the old ones.
We will still call the old upload path where required (e.g. Durable Object migration or Service Worker format).
#6563 da48a70 Thanks @threepointone! - chore: remove the warning about local mode flag being removed in the future
#6595 0a76d7e Thanks @vicb! - feat: update unenv to the latest available version
#5738 c2460c4 Thanks @penalosa! - fix: Prevent spaces in names when validating
#6586 72ea742 Thanks @penalosa! - chore: Improve Miniflare CRON warning wording
#6593 f097cb7 Thanks @vicb! - fix: remove experimental: prefix requirement for nodejs_compat_v2
See https://jira.cfdata.org/browse/DEVDASH-218
#6572 0d83428 Thanks @penalosa! - fix: Show a clearer user error when trying to use a python worker without the python_workers compatibility flag specified
#6589 f4c8cea Thanks @vicb! - feat: update unenv to the latest available version
Updated dependencies [45ad2e0]:
Updated dependencies [`6c057d1`]:
#6548 439e63a Thanks @garvit-gupta! - fix: Fix Vectorize getVectors, deleteVectors payload in Wrangler Client; VS-271
#6554 46aee5d Thanks @andyjessop! - fix: nodejs_compat flags no longer error when running wrangler types --x-include-runtime
#6548 439e63a Thanks @garvit-gupta! - fix: Add content-type header to Vectorize POST operations; #6516/VS-269
#6566 669ec1c Thanks @penalosa! - fix: Ensure esbuild warnings are logged when running wrangler deploy
Updated dependencies [6c057d1]:
Updated dependencies [`b0e2f0b`, `f5bde66`]:
#6511 e75c581 Thanks @petebacondarwin! - fix: allow Pages projects to use `experimental:nodejs_compat_v2" flag
Fixes #6288
Updated dependencies [b0e2f0b, f5bde66]:
Replaces #6471, which was too verbose.
#6530 d0ecc6a Thanks @WalshyDev! - fix: fixed wrangler versions upload printing bindings twice
#6502 a9b4f25 Thanks @garvit-gupta! - fix: Fix Vectorize List MetadataIndex Http Method
#6508 56a3de2 Thanks @petebacondarwin! - fix: move the Windows C++ redistributable warning so it is only shown if there is an actual access violation
Replaces #6471, which was too verbose.
Fixes #6170
As well as providing paths to custom HTTPS certificate files, it is now possible to use WRANGLER_HTTPS_KEY_PATH and WRANGLER_HTTPS_CERT_PATH environme
#6479 3c24d84 Thanks @petebacondarwin! - feat: allow HTTPS custom certificate paths to be provided by a environment variables
As well as providing paths to custom HTTPS certificate files, it is now possible to use WRANGLER_HTTPS_KEY_PATH and WRANGLER_HTTPS_CERT_PATH environment variables.
Specifying the file paths at the command line overrides specifying in environment variables.
Fixes #5997
#6471 0d85f24 Thanks @petebacondarwin! - fix: add a helpful message on Windows when Miniflare fails to start
#6489 34bf393 Thanks @GregBrimble! - fix: Upload assets as JSON Lines (application/jsonl) rather than NDJSON (application/x-ndjson)
#6482 e24939c Thanks @RamIdeas! - fix: reimplement module aliasing so user-defined aliases take precedence over other plugins (eg unenv node.js polyfills)
Updated dependencies [00f340f]:
To avoid a breaking change, we have kept --count as an alias to --limit.
#6464 da9106c Thanks @AnantharamanSI! - feat: rename --count to --limit in wrangler d1 insights
This PR renames wrangler d1 insight's --count flag to --limit to improve clarity and conform to naming conventions.
To avoid a breaking change, we have kept --count as an alias to --limit.
#6451 515de6a Thanks @danielrs! - feat: whoami shows membership information when available
#6463 dbc6782 Thanks @AnantharamanSI! - feat: add queryEfficiency to wrangler d1 insights output
#6252 a2a144c Thanks @garvit-gupta! - feat: Enable Wrangler to operate on Vectorize V2 indexes
Updated dependencies [`d55eeca`]:
05082ad Thanks @petebacondarwin! - feat: support outputting ND-JSON files via an environment variable#6440 09b5092 Thanks @petebacondarwin! - fix: tweak the properties of the new Wrangler output file entries for better consistency
Updated dependencies [d55eeca]:
### Patch Changes - #6432 `cba2e25` Thanks @petebacondarwin! - fix: prevent crash when running wrangler dev due to missing dependency
cba2e25 Thanks @petebacondarwin! - fix: prevent crash when running wrangler dev due to missing dependencyThese changes do the ground work needed in order to add Assets support for Workers in wrangler dev. They implement the following:
#6392 c3e19b7 Thanks @taylorlee! - feat: log Worker startup time in the version upload command
#6370 8a3c6c0 Thanks @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:
workers-shared that hosts the Asset Server Worker, and the Router Workerin the futureAsset Server Worker in some very basic form, with basic configuration. Further behaviour implementation will follow in a subsequent PR#6392 c3e19b7 Thanks @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.
When using --localUpstream=example.com, the request.url would incorrectly be "example.com:8787" but is now "example.com".
#6318 dc576c8 Thanks @danlapid! - feat: Add a log for worker startup time in wrangler deploy
#6097 64f34e8 Thanks @RamIdeas! - feat: implements the --experimental-dev-env (shorthand: --x-dev-env) flag for wrangler pages dev
#6379 31aa15c Thanks @RamIdeas! - fix: clearer error message when trying to use Workers Sites or Legacy Assets with wrangler versions upload
#6367 7588800 Thanks @RamIdeas! - fix: implicitly cleanup (call stop()) in unstable_dev if the returned Promise rejected and the stop() function was not returned
#6330 cfbdede Thanks @RamIdeas! - fix: when the worker's request.url is overridden using the host or localUpstream, ensure port is 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-env and unstable_dev({ experimental: { devEnv: true } }).
#6365 13549c3 Thanks @WalshyDev! - fix: WASM modules meant that wrangler versions secret ... could not properly update the version. This has now been fixed.
Updated dependencies [a9021aa, 44ad2c7]:
This change adds a new experimental CLI flag (--experimental-assets) and configuration key (experimental_assets) for the new Workers + Assets work.
#6312 67c611a Thanks @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]:
When using any cloudchamber command the cloudchamber scope will now be added to the existing scopes instead of replacing them.
#4545 e5afae0 Thanks @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 373248e Thanks @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 a432a13 Thanks @CarmenPopoviciu! - feat: Add support for wrangler.jsonc
This commit adds support for wrangler.jsonc config file for Workers. This feature is available behind the --experimental-json-config flag (just like wrangler.json).
To use the new configuration file, add a wrangler.jsonc file to your Worker project and run wrangler dev --experimental-json-config or wrangler deploy --experimental-json-config.
Please note that this work does NOT add wrangler.json or wrangler.jsonc support for Pages projects!
#6168 1ee41ff Thanks @IRCody! - feature: Add list and remove subcommands to cloudchamber registries command.
#6331 e6ada07 Thanks @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.
The existing behavior of the assets config key/flag will change on August 15th.
#6295 ebc85c3 Thanks @andyjessop! - feat: introduce an experimental flag for wrangler types to dynamically generate runtime types according to the user's project configuration.
#6272 084d39e Thanks @emily-shen! - fix: add legacy-assets config and flag as alias of current assets behavior
assets config key/flag will change on August 15th.legacy-assets will preserve current functionality.Updated dependencies [`779c713`]:
#6267 957d668 Thanks @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 e7c06d7 Thanks @gabivlj! - fix: wrangler cloudchamber json errors are properly formatted
Updated dependencies [779c713]:
Wrangler will now send the duration and the total size of any sourcemaps uploaded with your Worker to Cloudflare if you have metrics enabled.
#6194 25afcb2 Thanks @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 eb201a3 Thanks @ottomated! - chore: Add types to DurableObjectNamespace type generation. For example:
interface Env {
OBJECT: DurableObjectNamespace<import("./src/index").MyDurableObject>;
}
#6245 e4abed3 Thanks @OilyLime! - feature: Add support for Hyperdrive over Access configs
#6255 d497e1e Thanks @rozenmd! - fix: teach wrangler init --from-dash about d1 bindings
This PR teaches wrangler init --from-dash about D1 bindings, so they aren't incorrectly added to the wrangler.toml as unsafe bindings.
#6258 4f524f2 Thanks @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 8bbd824 Thanks @petebacondarwin! - chore: Update config-schema.json for the wrangler.toml
#5955 db11a0f Thanks @harugon! - fix: correctly escape newlines in constructType function for multiline strings
This fix ensures that multiline strings are correctly handled by the constructType function. Newlines are now properly escaped to prevent invalid JavaScript code generation when using the wrangler types command. This improves robustness and prevents errors related to multiline string handling in environment variables and other configuration settings.
#6263 fa1016c Thanks @petebacondarwin! - fix: use cli script-name arg when deploying a worker with queue consumers
Updated dependencies [0d32448]:
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
#4925 7d4a4d0 Thanks @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 75f7928 Thanks @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 4b1e5bc Thanks @mattpocock! - fix: update tsconfig for Workers generated by wrangler init
in workerd detaching the waitUntil and passThroughOnException methods from the ExecutionContext object results in them throwing illegal invocation err
#6199 88313e5 Thanks @dario-piotrowicz! - fix: make sure getPlatformProxy's ctx methods throw illegal invocation errors like workerd
in workerd detaching the waitUntil and passThroughOnException methods from the ExecutionContext
object results in them throwing illegal invocation errors, such as for example:
export default {
async fetch(_request, _env, { waitUntil }) {
waitUntil(() => {}); // <-- throws an illegal invocation error
return new Response("Hello World!");
},
};
make sure that the same behavior is applied to the ctx object returned by getPlatformProxy
#5569 75ba960 Thanks @penalosa! - fix: Simplify wrangler pages download config:
The watch mode in pages dev for Advanced Mode projects is currently partially broken, as it only watches for changes in the "\_worker.js" file, but no
#6192 b879ce4 Thanks @petebacondarwin! - fix: do not report D1 user errors to Sentry
#6150 d993409 Thanks @CarmenPopoviciu! - fix: Fix pages dev watch mode [_worker.js]
The watch mode in pages dev for Advanced Mode projects is currently partially broken, as it only watches for changes in the "_worker.js" file, but not for changes in any of its imported dependencies. This means that given the following "_worker.js" file
import { graham } from "./graham-the-dog";
export default {
fetch(request, env) {
return new Response(graham)
}
}
pages dev will reload for any changes in the _worker.js file itself, but not for any changes in graham-the-dog.js, which is its dependency.
Similarly, pages dev will not reload for any changes in non-JS module imports, such as wasm/html/binary module imports.
This commit fixes all the aforementioned issues.
Sometimes, users want to replace modules with other modules. This commonly happens inside a third party dependency itself. As an example, a user might
#6167 e048958 Thanks @threepointone! - feature: alias modules in the worker
Sometimes, users want to replace modules with other modules. This commonly happens inside a third party dependency itself. As an example, a user might have imported node-fetch, which will probably never work in workerd. You can use the alias config to replace any of these imports with a module of your choice.
Let's say you make a fetch-nolyfill.js
export default fetch; // all this does is export the standard fetch function`
You can then configure wrangler.toml like so:
# ...
[alias]
"node-fetch": "./fetch-nolyfill"
So any calls to import fetch from 'node-fetch'; will simply use our nolyfilled version.
You can also pass aliases in the cli (for both dev and deploy). Like:
npx wrangler dev --alias node-fetch:./fetch-nolyfill
#6073 7ed675e Thanks @geelen! - Added D1 export support for local databases
#6149 35689ea Thanks @RamIdeas! - refactor: React-free hotkeys implementation, behind the --x-dev-env flag
#6022 7951815 Thanks @CarmenPopoviciu! - fix: Fix pages dev watch mode [Functions]
The watch mode in pages dev for Pages Functions projects is currently partially broken, as it only watches for file system changes in the
"/functions" directory, but not for changes in any of the Functions' dependencies. This means that given a Pages Function math-is-fun.ts, defined as follows:
import { ADD } from "../math/add";
export async function onRequest() {
return new Response(`${ADD} is fun!`);
}
pages dev will reload for any changes in math-is-fun.ts itself, but not for any changes in math/add.ts, which is its dependency.
Similarly, pages dev will not reload for any changes in non-JS module imports, such as wasm/html/binary module imports.
This commit fixes all these things, plus adds some extra polish to the pages dev watch mode experience.
#6164 4cdad9b Thanks @threepointone! - fix: use account id for listing zones
Fixes https://github.com/cloudflare/workers-sdk/issues/4944
Trying to fetch /zones fails when it spans more than 500 zones. The fix to use an account id when doing so. This patch passes the account id to the zones call, threading it through all the functions that require it.
#6180 b994604 Thanks @Skye-31! - Fix: pass env to getBindings to support reading .dev.vars.{environment}
https://github.com/cloudflare/workers-sdk/pull/5612 added support for selecting the environment of config used, but it missed passing it to the code that reads .dev.vars.{environment}
Closes #5641
#6124 d03b102 Thanks @RamIdeas! - feat: url and inspectorUrl properties have been exposed on the worker object returned by new unstable_DevEnv().startWorker(options)
#6147 02dda3d Thanks @penalosa! - refactor: React free dev registry
#6127 1568c25 Thanks @DaniFoldi! - fix: Bump ws dependency
#6140 4072114 Thanks @petebacondarwin! - fix: add extra error logging to auth response errors
#6160 9466531 Thanks @sm-bean! - fix: removes unnecessary wrangler tail warning against resetting durable object
fixes https://jira.cfdata.org/browse/STOR-3318
#6142 9272ef5 Thanks @dario-piotrowicz! - fix: improve the getPlatformProxy configPath option ts-doc comment to clarify its behavior
Updated dependencies [42a7930, 7ed675e, 1568c25]:
wrangler versions secret put allows for you to add/update a secret even if the latest version is not fully deployed. A new version with this secret wi
#5950 0075621 Thanks @WalshyDev! - feat: add wrangler versions secret put, wrangler versions secret bulk and wrangler versions secret list
wrangler versions secret put allows for you to add/update a secret even if the latest version is not fully deployed. A new version with this secret will be created, the existing secrets and config are copied from the latest version.
wrangler versions secret bulk allows you to bulk add/update multiple secrets at once, this behaves the same as secret put and will only make one new version.
wrangler versions secret list lists the secrets available to the currently deployed versions. wrangler versions secret list --latest-version or wrangler secret list will list for the latest version.
Additionally, we will now prompt for extra confirmation if attempting to rollback to a version with different secrets than the currently deployed.
#6118 1621992 Thanks @WalshyDev! - fix: rollback in the case of a secret change, the prompt meant to show was not showing due to the spinner in an interactive env. It will now properly show.
chore: improve the view of wrangler versions view and change up copy a little for versions secret commands.
#6105 26855f3 Thanks @helloimalastair! - feat: Add help messages to all invalid r2 commands
#3735 9c7df38 Thanks @lrapoport-cf! - chore: Cleanup wrangler --help output
This commit cleans up and standardizes the look and feel of all wrangler commands as displayed by wrangler --help and wrangler <cmd> --help.
#6080 e2972cf Thanks @threepointone! - chore: run eslint (with react config) on workers-playground/wrangler
This enables eslint (with our react config) for the workers-playground project. Additionally, this enables the react-jsx condition in relevant tsconfig/eslint config, letting us write jsx without having React in scope.
#6001 d39d595 Thanks @penalosa! - chore: changes to how wrangler dev launches your worker, behind the experimental --x-dev-env flag
#5214 05c5607 Thanks @penalosa! - feat: Experimental file based service discovery when running multiple Wrangler instances locally. To try it out, make sure all your local Wrangler instances are running with the --x-registry flag.
Updated dependencies [7d02856, d4e1e9f]:
This commit adds a small QOL improvement to init (to be deprecated in the future), for those who still use this wrangler command.
#5995 374bc44 Thanks @petebacondarwin! - feat: allow Durable Object migrations to be overridable in environments
By making the migrations key inheritable, users can provide different migrations
for each wrangler.toml environment.
Resolves #729
#6039 dc597a3 Thanks @petebacondarwin! - fix: hybrid nodejs compat now supports requiring the default export of a CJS module
Fixes #6028
#6051 15aff8f Thanks @threepointone! - fix: Don't check expiry dates on custom certs
Fixes https://github.com/cloudflare/workers-sdk/issues/5964
For wrangler dev, we don't have to check whether certificates have expired when they're provided by the user.
#6052 b4c0233 Thanks @threepointone! - chore: Add .wrangler and .DS_Store to .gitignore generated by wrangler init
This commit adds a small QOL improvement to init (to be deprecated in the future), for those who still use this wrangler command.
#6050 a0c3327 Thanks @threepointone! - chore: Normalize more deps
This is the last of the patches that normalize dependencies across the codebase. In this batch: ws, vitest, zod , rimraf, @types/rimraf, ava, source-map, glob, cookie, @types/cookie, @microsoft/api-extractor, @types/mime, @types/yargs, devtools-protocol, @vitest/ui, execa, strip-ansi
This patch also sorts dependencies in every package.json
#6029 f5ad1d3 Thanks @threepointone! - chore: Normalize some dependencies in workers-sdk
This is the first of a few expected patches that normalize dependency versions, This normalizes undici, concurrently, @types/node, react, react-dom, @types/react, @types/react-dom, eslint, typescript. There are no functional code changes (but there are a couple of typecheck fixes).
#6046 c643a81 Thanks @threepointone! - chore: Normalize more dependencies.
Follow up to https://github.com/cloudflare/workers-sdk/pull/6029, this normalizes some more dependencies : get-port, chalk, yargs, toucan-js, @typescript-eslint/parser, @typescript-eslint/eslint-plugin, esbuild-register, hono, glob-to-regexp, @cloudflare/workers-types
#6058 31cd51f Thanks @threepointone! - chore: Quieter builds
This patch cleans up warnings we were seeing when doing a full build. Specifically:
@microsoft/api-extractor so it didn't complain that it didn't match the typescript version (that we'd recently upgraded)wrangler. We'll need to fix those, but we'll do that when we work on unstable_dev etc.#6043 db66101 Thanks @threepointone! - fix: avoid esbuild warning when running dev/bundle
I've been experimenting with esbuild 0.21.4 with wrangler. It's mostly been fine. But I get this warning every time
▲ [WARNING] Import "__INJECT_FOR_TESTING_WRANGLER_MIDDLEWARE__" will always be undefined because there is no matching export in "src/index.ts" [import-is-undefined]
.wrangler/tmp/bundle-Z3YXTd/middleware-insertion-facade.js:8:23:
8 │ .....(OTHER_EXPORTS.__INJECT_FOR_TESTING_WRANGLER_MIDDLEWARE__ ?? []),
╵
This is because esbuild@0.18.5 enabled a warning by default whenever an undefined import is accessed on an imports object. However we abuse imports to inject stuff in middleware.test.ts. A simple fix is to only inject that code in tests.
#6062 267761b Thanks @WalshyDev! - fix: typo in wrangler d1 execute saying "Databas" instead of "Database"
#6064 84e6aeb Thanks @helloimalastair! - fix: Wrangler is now able to upload files to local R2 buckets above the 300 MiB limit
Updated dependencies [a0c3327, f5ad1d3, 31cd51f]:
It turns out that ESBuild paths are case insensitive, which can result in path collisions between polyfills for globalThis.performance and globalThis.
#6025 122ef06 Thanks @IgorMinar! - fix: avoid path collisions between performance and Performance Node.js polyfills
It turns out that ESBuild paths are case insensitive, which can result in path collisions between polyfills for globalThis.performance and globalThis.Performance, etc.
This change ensures that we encode all global names to lowercase and decode them appropriately.
#6009 169a9fa Thanks @RamIdeas! - fix: reduce the number of parallel file reads on Windows to avoid EMFILE type errors
Fixes #1586
53acdbc Thanks @petebacondarwin! - fix: warn if user tries normal deploy when in the middle of a gradual version rollout
Updated dependencies [c4146fc]:
This PR updates wrangler d1 insights to accept arbitrary timePeriod values up to 31 days.
### Patch Changes - #6002 `f1f1834` Thanks @GregBrimble! - Revert a change in 3.60.0 which incorrectly batched assets for Pages uploads (https://githu
f1f1834 Thanks @GregBrimble! - Revert a change in 3.60.0 which incorrectly batched assets for Pages uploads (https://github.com/cloudflare/workers-sdk/pull/5632).The old command is now deprecated (but still functional) and will be removed in a future release. The new command is now more consistent with the rest…
#5878 1e68fe5 Thanks @IgorMinar! - feat: add experimental support for hybrid Node.js compatibility
This feature is experimental and not yet available for general consumption.
Use a combination of workerd Node.js builtins (behind the experimental:nodejs_compat_v2 flag) and
Unenv polyfills (configured to only add those missing from the runtime) to provide a new more effective
Node.js compatibility approach.
#5988 e144f63 Thanks @RamIdeas! - feature: rename the wrangler secret:bulk command to wrangler secret bulk
The old command is now deprecated (but still functional) and will be removed in a future release. The new command is now more consistent with the rest of the wrangler CLI commands.
#5989 35b1a2f Thanks @RamIdeas! - feature: rename wrangler kv:... commands to wrangler kv ...
The old commands are now deprecated (but still functional) and will be removed in a future release. The new commands are now more consistent with the rest of the wrangler CLI commands.
#5861 1cc52f1 Thanks @zebp! - feat: allow for Pages projects to upload sourcemaps
Pages projects can now upload sourcemaps for server bundles to enable remapped stacktraces in realtime logs when deployed with upload_source_map set to true in wrangler.toml.
#5939 21573f4 Thanks @penalosa! - refactor: Adds the experimental flag --x-dev-env which opts in to using an experimental code path for wrangler dev and wrangler dev --remote. There should be no observable behaviour changes when this flag is enabled.
#5934 bac79fb Thanks @dbenCF! - fix: Update create KV namespace binding details message for easier implementation
#5927 6f83641 Thanks @CarmenPopoviciu! - fix: Clean pages dev terminal ouput
This work includes a series of improvements to the pages dev terminal output, in an attempt to make this output more structured, organised, cleaner, easier to follow, and therefore more helpful for our users <3
#5960 e648825 Thanks @petebacondarwin! - fix: avoid injecting esbuild watch stubs into production Worker code
When we added the ability to include additional modules in the deployed bundle of a Worker, we inadvertently also included some boiler plate code that is only needed at development time.
This fix ensures that this code is only injected if we are running esbuild in watch mode
(e.g. wrangler dev) and not when building for deployment.
It is interesting to note that this boilerplate only gets included in the production code if there is an import of CommonJS code in the Worker, which esbuild needs to convert to an ESM import.
Fixes #4269
Updated dependencies [ab95473]:
By setting WRANGLER_DISABLE_EXPERIMENTAL_WARNING to any truthy value, these warnings will be hidden.
#5963 bf803d7 Thanks @Skye-31! - Feature: Add support for hiding the "unsafe" fields are experimental warning using an environment variable
By setting WRANGLER_DISABLE_EXPERIMENTAL_WARNING to any truthy value, these warnings will be hidden.
bdbb7f8]:
The experimental "assets" field can be either a string or an object. However the type definition marks it only as an object. This is a problem because
93b98cb Thanks @WalshyDev! - feature: allow for writing authentication details per API environment. This allows someone targetting staging to have their staging auth details saved separately from production, this saves them logging in and out when switching environments.#5938 9e4d8bc Thanks @threepointone! - fix: let "assets" in wrangler.toml be a string
The experimental "assets" field can be either a string or an object. However the type definition marks it only as an object. This is a problem because we use this to generate the json schema, which gets picked up by vscode's even better toml extension, and shows it to be an error when used with a string (even though it works fine). The fix is to simply change the type definition to add a string variant.
#5758 8e5e589 Thanks @Jackenmen! - fix: use correct type for AI binding instead of unknown
Updated dependencies [e0e7725]:
Updated dependencies [`64ccdd6`, `4458a9e`]:
#5905 53f22a0 Thanks @penalosa! - fix: Remove WARP certificate injection. Instead, you should ensure that any custom certificates that are needed are included in NODE_EXTRA_CA_CERTS.
#5930 57daae0 Thanks @WalshyDev! - chore: improve error message when updating secret for a non-deployed latest version.
#5703 a905f31 Thanks @penalosa! - fix: Don't use ExportedHandler["middleware"] for injecting middleware
Updated dependencies [64ccdd6, 4458a9e]:
If a Pages project fails to deploy, wrangler pages deploy will log an error message, but exit successfully. It should instead throw a FatalError.
#5859 f2ceb3a Thanks @w-kuhn! - fix: queue consumer max_batch_timeout should accept a 0 value
#5862 441a05f Thanks @CarmenPopoviciu! - fix: wrangler pages deploy should fail if deployment was unsuccessful
If a Pages project fails to deploy, wrangler pages deploy will log
an error message, but exit successfully. It should instead throw a
FatalError.
#5812 d5e00e4 Thanks @thomasgauvin! - fix: remove Hyperdrive warning for local development.
Hyperdrive bindings are now supported when developing locally with Hyperdrive. We should update our logs to reflect this.
#5626 a12b031 Thanks @RamIdeas! - chore: ignore workerd output (error: CODE_MOVED) not intended for end-user devs
Today, if uploading a Pages Function, or deploying a Pages project fails for whatever reason, there’s no feedback shown to the user. Worse yet, the sh
#5696 7e97ba8 Thanks @geelen! - feature: Improved d1 execute --file --remote performance & added support for much larger SQL files within a single transaction.
#5819 63f7acb Thanks @CarmenPopoviciu! - fix: Show feedback on Pages project deployment failure
Today, if uploading a Pages Function, or deploying a Pages project fails for whatever reason, there’s no feedback shown to the user. Worse yet, the shown message is misleading, saying the deployment was successful, when in fact it was not:
✨ Deployment complete!
This commit ensures that we provide users with:
#5814 2869e03 Thanks @CarmenPopoviciu! - fix: Display correct global flags in wrangler pages --help
Running wrangler pages --help will list, amongst others, the following global flags:
-j, --experimental-json-config
-c, --config
-e, --env
-h, --help
-v, --version
This is not accurate, since flags such as --config, --experimental-json-config, or env are not supported by Pages.
This commit ensures we display the correct global flags that apply to Pages.
#5818 df2daf2 Thanks @WalshyDev! - chore: Deprecate usage of the deployment object on the unsafe metadata binding in favor of the new version_metadata binding.
If you're currently using the old binding, please move over to the new version_metadata binding by adding:
[version_metadata]
binding = "CF_VERSION_METADATA"
and updating your usage accordingly. You can find the docs for the new binding here: https://developers.cloudflare.com/workers/runtime-apis/bindings/version-metadata
#5838 609debd Thanks @petebacondarwin! - fix: update undici to the latest version to avoid a potential vulnerability
#5832 86a6e09 Thanks @petebacondarwin! - fix: do not allow non-string values in bulk secret uploads
Prior to Wrangler 3.4.0 we displayed an error if the user tried to upload a JSON file that contained non-string secrets, since these are not supported by the Cloudflare backend.
This change reintroduces that check to give the user a helpful error message
rather than a cryptic workers.api.error.invalid_script_config error code.
Reduces the maximum bucket size from 50 MiB to 40 MiB.
151bc3d Thanks @penalosa! - feat: Support mtls_certificates and browser bindings when using wrangler.toml with a Pages project#5813 9627cef Thanks @GregBrimble! - fix: Upload Pages project assets with more grace
Updated dependencies [0725f6f, 89b6d7f]:
This change updates the miniflare's queue broker to support delayed delivery of messages, both when sending the message from a producer and when retry
#5570 66bdad0 Thanks @sesteves! - feature: support delayed delivery in the miniflare's queue simulator.
This change updates the miniflare's queue broker to support delayed delivery of messages, both when sending the message from a producer and when retrying the message from a consumer.
#5740 97741db Thanks @WalshyDev! - chore: log "Version ID" in wrangler deploy, wrangler deployments list, wrangler deployments view and wrangler rollback to support migration from the deprecated "Deployment ID". Users should update any parsing to use "Version ID" before "Deployment ID" is removed.
#5754 f673c66 Thanks @RamIdeas! - fix: when using custom builds, the wrangler dev proxy server was sometimes left in a paused state
This could be observed as the browser loading indefinitely, after saving a source file (unchanged) when using custom builds. This is now fixed by ensuring the proxy server is unpaused after a short timeout period.
Updated dependencies [66bdad0, 9b4af8a]:
One column per quarter.