chore(deps): update dependency wrangler to v3 #2

renovate · 2023-06-11T02:33:02Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
wrangler (source)	`2.21.1` -> `3.64.0`

Release Notes

cloudflare/workers-sdk (wrangler)

`v3.64.0`

Minor Changes

#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.

Patch Changes

#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

`v3.63.2`

Patch Changes

#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:
- Don't include inheritable keys in the production override if they're equal to production
- Only create a preview environment if needed, otherwise put the preview config at the top level

`v3.63.1`

Compare Source

Patch Changes

#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.

`v3.63.0`

Compare Source

Minor Changes

#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:

`v3.62.0`

Compare Source

Minor Changes

#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.

Patch Changes

#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]:
- [email protected]
- @cloudflare/kv-asset-handler @0.3.4

`v3.61.0`

Compare Source

Minor Changes

#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

Patch Changes

#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:
- fixtures/remix-pages-app had a bunch of warnings about impending features that it should be upgraded to, so I did that. (tbh this one needs a full upgrade of packages, but we'll get to that later when we're upgrading across the codebase)
- updated @microsoft/api-extractor so it didn't complain that it didn't match the typescript version (that we'd recently upgraded)
- it also silenced a bunch of warnings when exporting types from wrangler. We'll need to fix those, but we'll do that when we work on unstable_dev etc.
- workers-playground was complaining about the size of the bundle being generated, so I increased the limit on it
#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 [email protected] 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]:
- [email protected]
- @cloudflare/kv-asset-handler @0.3.3

`v3.60.3`

Compare Source

Patch Changes

#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]:
- [email protected]

`v3.60.2`

Compare Source

Patch Changes

#5307 e6a3d24 Thanks @achanda! - fix: add more timePeriods to wrangler d1 insights

This PR updates wrangler d1 insights to accept arbitrary timePeriod values up to 31 days.

`v3.60.1`

Compare Source

Patch Changes

#6002 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).

`v3.60.0`

Compare Source

Minor Changes

#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.

Patch Changes

#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]:
- [email protected]

`v3.59.0`

Compare Source

Minor Changes

#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.

Patch Changes

Updated dependencies [bdbb7f8]:
- [email protected]

`v3.58.0`

Compare Source

Minor Changes

#5933 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.

Patch Changes

#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]:
- [email protected]

`v3.57.2`

Compare Source

Patch Changes

#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]:
- [email protected]

`v3.57.1`

Compare Source

Patch Changes

#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

`v3.57.0`

Compare Source

Minor Changes

#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:
- the correct feedback with respect to their Pages deployment
- the appropriate messaging depending on the status of their project's deployment status
- the appropriate logs in case of a deployment failure
#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

Patch Changes

#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.

`v3.56.0`

Compare Source

Minor Changes

#5712 151bc3d Thanks @penalosa! - feat: Support mtls_certificates and browser bindings when using wrangler.toml with a Pages project

Patch Changes

#5813 9627cef Thanks @GregBrimble! - fix: Upload Pages project assets with more grace
- Reduces the maximum bucket size from 50 MiB to 40 MiB.
- Reduces the maximum asset count from 5000 to 2000.
- Allows for more retries (with increased sleep between attempts) when encountering an API gateway failure.
Updated dependencies [0725f6f, 89b6d7f]:
- [email protected]

`v3.55.0`

Compare Source

Minor Changes

#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.

Patch Changes

#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]:
- [email protected]

`v3.53.1`

Compare Source

Patch Changes

#5091 6365c90 Thanks @Cherry! - fix: better handle dashes and other invalid JS identifier characters in wrangler types generation for vars, bindings, etc.

Previously, with the following in your wrangler.toml, an invalid types file would be generated:
```
[vars]
some-var = "foobar"
```
Now, the generated types file will be valid:
```
interface Env {
	"some-var": "foobar";
}
```
#5748 27966a4 Thanks @penalosa! - fix: Load sourcemaps relative to the entry directory, not cwd.
#5746 1dd9f7e Thanks @petebacondarwin! - fix: suggest trying to update Wrangler if there is a newer one available after an unexpected error
#5226 f63e7a5 Thanks @DaniFoldi! - fix: remove second Wrangler banner from wrangler dispatch-namespace rename

`v3.53.0`

Compare Source

Minor Changes

#5604 327a456 Thanks @dario-piotrowicz! - feat: add support for environments in getPlatformProxy

allow getPlatformProxy to target environments by allowing users to specify an environment option

Example usage:
```
const { env } = await getPlatformProxy({
	environment: "production",
});
```

Patch Changes

#5705 4097759 Thanks @G4brym! - Add staging flag to AI binding

`v3.52.0`

Compare Source

Minor Changes

#5666 81d9615 Thanks @CarmenPopoviciu! - fix: Fix Pages config validation around Durable Objects

Today Pages cannot deploy Durable Objects itself. For this reason it is mandatory that when declaring Durable Objects bindings in the config file, the script_name is specified. We are currently not failing validation if
script_name is not specified but we should. These changes fix that.

Patch Changes

#5610 24840f6 Thanks @SuperchupuDev! - Mark ts-json-schema-generator as a dev dependency
#5669 a7e36d5 Thanks @dario-piotrowicz! - fix: fix broken Durable Object local proxying (when no cf property is present)

A regression was introduced in wrangler 3.46.0 (https://github.com/cloudflare/workers-sdk/pull/5215)
which made it so that missing Request#cf properties are serialized as "undefined", this in turn
throws a syntax parse error when such values are parsed via JSON.parse breaking the communication
with Durable Object local proxies. Fix such issue by serializing missing Request#cf properties as
"{}" instead.
#5616 c6312b5 Thanks @webbertakken! - fix: broken link to durable object migrations docs
#5482 1b7739e Thanks @DaniFoldi! - docs: show new Discord url everywhere for consistency. The old URL still works, but https://discord.cloudflare.com is preferred.
Updated dependencies [3a0d735, 1b7739e]:
- [email protected]
- @cloudflare/kv-asset-handler @0.3.2

`v3.51.2`

Compare Source

Patch Changes

#5652 ccb9d3d Thanks @petebacondarwin! - chore: re-release due to broken build

`v3.51.0`

Compare Source

Minor Changes

#5477 9a46e03 Thanks @pmiguel! - feature: Changed Queues client to use the new QueueId and ConsumerId-based endpoints.
#5172 fbe1c9c Thanks @GregBrimble! - feat: Allow marking external modules (with --external) to avoid bundling them when building Pages Functions

It's useful for Pages Plugins which want to declare a peer dependency.

Patch Changes

#5585 22f5841 Thanks @geelen! - Updates wrangler d1 export to handle larger DBs more efficiently
Updated dependencies [c9f081a, c9f081a]:
- [email protected]

`v3.50.0`

Compare Source

Minor Changes

#5587 d95450f Thanks @CarmenPopoviciu! - fix: pages functions build-env should throw error if invalid Pages config file is found
#5572 65aa21c Thanks @CarmenPopoviciu! - fix: fix pages function build-env to exit with code rather than throw fatal error

Currently pages functions build-env throws a fatal error if a config file does not exit, or if it is invalid. This causes issues for the CI system. We should instead exit with a specific code, if any of those situations arises.
#5291 ce00a44 Thanks @pmiguel! - feature: Added bespoke OAuth scope for Queues management.

Patch Changes

Updated dependencies [08b4908]:
- [email protected]

`v3.49.0`

Compare Source

Minor Changes

#5549 113ac41 Thanks @penalosa! - feat: Support wrangler pages secret put|delete|list|bulk
#5550 4f47f74 Thanks @penalosa! - feat: Generate a JSON schema for the Wrangler package & use it in templates
#5561 59591cd Thanks @ocsfrank! - feat: update R2 CreateBucket action to include the storage class in the request body

Patch Changes

#5374 7999dd2 Thanks @maxwellpeterson! - fix: Improvements to --init-from-dash

Adds user-specified CPU limit to wrangler.toml if one exists. Excludes usage_model from wrangler.toml in all cases, since this field is deprecated and no longer used.
#5553 dcd65dd Thanks @rozenmd! - fix: refactor d1's time-travel compatibility check
#5380 57d5658 Thanks @GregBrimble! - fix: Respect --no-bundle when deploying a _worker.js/ directory in Pages projects
#5536 a7aa28a Thanks @Cherry! - fix: resolve a regression where wrangler pages dev would bind to port 8787 by default instead of 8788 since [email protected]
Updated dependencies [9575a51]:
- [email protected]

`v3.48.0`

Compare Source

Minor Changes

#5429 c5561b7 Thanks @ocsfrank! - R2 will introduce storage classes soon. Wrangler allows you to interact with storage classes once it is
enabled on your account.

Wrangler supports an -s flag that allows the user to specify a storage class when creating a bucket,
changing the default storage class of a bucket, and uploading an object.
```
wrangler r2 bucket create ia-bucket -s InfrequentAccess
wrangler r2 bucket update storage-class my-bucket -s InfrequentAccess
wrangler r2 object put bucket/ia-object -s InfrequentAccess --file foo
```

Patch Changes

#5531 887150a Thanks @penalosa! - fix: Write wrangler pages functions build-env to file rather than stdout
#5526 bafbd67 Thanks @rozenmd! - fix: teach wrangler d1 create about Australia

Minor Changes

#5506 7734f80 Thanks @penalosa! - feat: Add interactive prompt to wrangler pages download config if an existing wrangler.toml file exists

`v3.46.0`

Compare Source

Minor Changes

#5282 b7ddde1 Thanks @maxwellpeterson! - feature: Add source map support for Workers

Adds the source_maps boolean config option. When enabled, source maps included in the build output are uploaded alongside the built code modules. Uploaded source maps can then be used to remap stack traces emitted by the Workers runtime.

#5215 cd03d1d Thanks @GregBrimble! - feature: support named entrypoints in service bindings

This change allows service bindings to bind to a named export of another Worker. As an example, consider the following Worker named bound:

import { WorkerEntrypoint } from "cloudflare:workers";

export class EntrypointA extends WorkerEntrypoint {
	fetch(request) {
		return new Response("Hello from entrypoint A!");
	}
}

export const entrypointB: ExportedHandler = {
	fetch(request, env, ctx) {
		return new Response("Hello from entrypoint B!");
	}
};

export default <ExportedHandler>{
	fetch(request, env, ctx) {
		return new Response("Hello from the default entrypoint!");
	}
};

Up until now, you could only bind to the default entrypoint. With this change, you can bind to EntrypointA or entrypointB too using the new entrypoint option:

[[services]]
binding = "SERVICE"
service = "bound"
entrypoint = "EntrypointA"

To bind to named entrypoints with wrangler pages dev, use the # character:

$ wrangler pages dev --service=SERVICE=bound#EntrypointA

Patch Changes

#5215 cd03d1d Thanks @GregBrimble! - fix: ensure request url and cf properties preserved across service bindings

Previously, Wrangler could rewrite url and cf properties when sending requests via service bindings or Durable Object stubs. To match production behaviour, this change ensures these properties are preserved.
Updated dependencies [cd03d1d, 6c3be5b, cd03d1d, cd03d1d]:
- [email protected]

`v3.45.0`

Compare Source

Minor Changes

#5377 5d68744 Thanks @CarmenPopoviciu! - feat: Add wrangler.toml support in wrangler pages deploy

As we are adding wrangler.toml support for Pages, we want to ensure that wrangler pages deploy works with a configuration file.
#5471 489b9c5 Thanks [@zebp](https://togith

Configuration

📅 Schedule: Branch creation - "every weekend" in timezone Asia/Makassar, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

renovate bot added the renovate label Jun 11, 2023

renovate bot force-pushed the renovate/wrangler-3.x branch 2 times, most recently from 8fa23a6 to d94020c Compare June 21, 2023 05:33

renovate bot force-pushed the renovate/wrangler-3.x branch 3 times, most recently from 210709d to a09e166 Compare July 12, 2023 05:33

renovate bot force-pushed the renovate/wrangler-3.x branch 3 times, most recently from 097439d to 699906a Compare July 22, 2023 02:38

renovate bot force-pushed the renovate/wrangler-3.x branch 2 times, most recently from 5172dbb to 9053850 Compare July 29, 2023 02:08

renovate bot force-pushed the renovate/wrangler-3.x branch 3 times, most recently from e2f5496 to c58d43c Compare August 12, 2023 08:10

renovate bot force-pushed the renovate/wrangler-3.x branch 2 times, most recently from 945c9e9 to 40c5020 Compare August 20, 2023 02:24

renovate bot force-pushed the renovate/wrangler-3.x branch 2 times, most recently from a76a410 to 8023b73 Compare September 3, 2023 14:44

renovate bot force-pushed the renovate/wrangler-3.x branch 2 times, most recently from b743db1 to d8a239d Compare September 10, 2023 11:59

renovate bot force-pushed the renovate/wrangler-3.x branch 3 times, most recently from 74c7ee1 to 4ef9d61 Compare September 21, 2023 05:35

renovate bot force-pushed the renovate/wrangler-3.x branch 4 times, most recently from cc42cec to 0641c78 Compare September 30, 2023 02:53

renovate bot force-pushed the renovate/wrangler-3.x branch 3 times, most recently from 0aeee33 to a511c0c Compare October 12, 2023 05:14

renovate bot force-pushed the renovate/wrangler-3.x branch 4 times, most recently from 46a04eb to 8a092e3 Compare April 5, 2024 05:49

renovate bot force-pushed the renovate/wrangler-3.x branch 2 times, most recently from faf1855 to eb13e10 Compare April 12, 2024 23:46

renovate bot force-pushed the renovate/wrangler-3.x branch 3 times, most recently from b6ea81d to 7ed1ec0 Compare April 20, 2024 02:55

renovate bot force-pushed the renovate/wrangler-3.x branch 3 times, most recently from e2d6bc7 to 58befba Compare May 1, 2024 05:48

renovate bot force-pushed the renovate/wrangler-3.x branch 2 times, most recently from f51d206 to 2f3e0d1 Compare May 4, 2024 05:46

renovate bot force-pushed the renovate/wrangler-3.x branch from 2f3e0d1 to c81a32f Compare May 10, 2024 17:54

renovate bot force-pushed the renovate/wrangler-3.x branch 2 times, most recently from 1c3c5cb to 4f2e8ef Compare May 28, 2024 20:45

renovate bot force-pushed the renovate/wrangler-3.x branch 3 times, most recently from b01def8 to 6fbee6d Compare June 8, 2024 05:23

renovate bot force-pushed the renovate/wrangler-3.x branch 2 times, most recently from dece480 to 09c5164 Compare June 15, 2024 05:47

renovate bot force-pushed the renovate/wrangler-3.x branch 2 times, most recently from 8dbcdc2 to 0a4b993 Compare June 22, 2024 21:00

renovate bot force-pushed the renovate/wrangler-3.x branch from 0a4b993 to a30a82f Compare June 26, 2024 11:46

renovate bot force-pushed the renovate/wrangler-3.x branch 3 times, most recently from 4c47479 to 27fc941 Compare July 10, 2024 05:04

chore(deps): update dependency wrangler to v3

93f5544

renovate bot force-pushed the renovate/wrangler-3.x branch from 27fc941 to 93f5544 Compare July 12, 2024 20:20

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(deps): update dependency wrangler to v3 #2

chore(deps): update dependency wrangler to v3 #2

renovate bot commented Jun 11, 2023 •

edited

Loading

chore(deps): update dependency wrangler to v3 #2

Are you sure you want to change the base?

chore(deps): update dependency wrangler to v3 #2

Conversation

renovate bot commented Jun 11, 2023 • edited Loading

Release Notes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Minor Changes

Patch Changes

Minor Changes

Configuration

renovate bot commented Jun 11, 2023 •

edited

Loading