Closed threepointone closed 3 months ago
Latest commit: 4d9dd57bb4dbf327c17a08e94d00378e4b699669
The changes in this PR will be included in the next version bump.
Not sure what this means? Click here to learn what changesets are.
Click here if you're a maintainer who wants to add another changeset to this PR
A wrangler prerelease is available for testing. You can install this latest build in your project with:
npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/9519135628/npm-package-wrangler-6043
You can reference the automatically updated head of this PR with:
npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/prs/6043/npm-package-wrangler-6043
Or you can use npx
with this latest build directly:
npx https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/9519135628/npm-package-wrangler-6043 dev path/to/script.js
wrangler@3.60.3
includes the following runtime dependencies:
Package | Constraint | Resolved |
---|---|---|
miniflare |
workspace:* | 3.20240610.0 |
workerd |
1.20240610.1 | 1.20240610.1 |
workerd --version |
1.20240610.1 | 2024-06-10 |
Please ensure constraints are pinned, and miniflare
/workerd
minor versions match.
Congratulations @threepointone, you just earned a holobyte! Here it is: https://holopin.io/holobyte/clxez4jka49160el2effqa3gt
This badge can only be claimed by you, so make sure that your GitHub account is linked to your Holopin account. You can manage those preferences here: https://holopin.io/account. Or if you're new to Holopin, you can simply sign up with GitHub, which will do the trick!
(Another simpler take on https://github.com/cloudflare/workers-sdk/pull/5999, inspired by https://github.com/cloudflare/workers-sdk/pull/6006)
I've been experimenting with esbuild 0.21.4 with wrangler. It's mostly been fine. But I get this warning every time
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.