You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm sure R2 isn't the only product with this issue, but:
Here's the output of wrangler dev with a bucket bound:
> wrangler dev ./src/index.ts
⛅️ wrangler 3.78.4 (update available 3.78.8)
-------------------------------------------------------
Your worker has access to the following bindings:
- R2 Buckets:
- BUCKET: asdfasdf
⎔ Starting local server...
[wrangler:inf] Ready on http://localhost:8787
When you have a bucket on R2 named asdfasdf, it's really confusing why your Worker is 404ing fetches from that bucket in wrangler dev.
The text was updated successfully, but these errors were encountered:
Wonder if this should be a part of a bigger UX improvement?
Even a simple BINDING_NAME: <name> (local mode) for all of the bindings that run locally would be much better than the current.
Describe the solution
I'm sure R2 isn't the only product with this issue, but:
Here's the output of wrangler dev with a bucket bound:
When you have a bucket on R2 named asdfasdf, it's really confusing why your Worker is 404ing fetches from that bucket in
wrangler dev
.The text was updated successfully, but these errors were encountered: