so there is a chance we see this feature for workers in the future? - Cloudflare Developers

© 2026 Hedgehog Software, LLC

More

Communities Docs About Terms Privacy

TheSunSide

T

TheSunSide•8/19/22, 12:13 AM

If you're using an env, it'll do WORKERNAME-ENVNAME

TheSunSide

T

TheSunSide•8/19/22, 12:13 AM

so there no way to "accumulate them" rn

Salzian

SSalzian so there is a chance we see this feature for workers in the future?

Cyb3r-Jak3

C

Cyb3r-Jak3•8/19/22, 12:14 AM

Yes the feature will most likely come back

Salzian

S

SalzianOP•8/19/22, 12:14 AM

Alright. It's not a hindrance, obviously, I was just confused by this feature not being available for workers. I thought I was doing something wrong in the TOML file. Thanks @thesunside @Cyb3r-Jok3

Salzian

SSalzian Alright. It's not a hindrance, obviously, I was just confused by this feature no...

TheSunSide

T

TheSunSide•8/19/22, 12:15 AM

Yeah, it makes writing worker names a bit awkward

TheSunSide

T

TheSunSide•8/19/22, 12:15 AM

*for bindings

Salzian

S

SalzianOP•8/19/22, 12:15 AM

Not using bindings just yet

I'm still experimenting with workers mostly.

TheSunSide

T

TheSunSide•8/19/22, 12:16 AM

oh well if you do, type the result name as the worker name pain

pain

Salzian

S

SalzianOP•8/19/22, 12:17 AM

Good to know. Maybe with environments coming back in the future, you can auto-bind to the corresponding environment

WillTolmie

W

WillTolmie•8/19/22, 12:37 PM

Anyone else struggling to get "wrangler dev" to work at the mo? Publish works fine, worker with graphql server runs nicely, but I get a 504 timeout on dev

jjjrmy

J

jjjrmy•8/19/22, 12:43 PM

I'm following the docs exactly?
npx wrangler pages dev dist --r2=BUCKETnpx wrangler pages dev dist --r2=BUCKET

> wrangler pages dev ./dist --r2=THEMES


✘ [ERROR] Unknown argument: r2

> wrangler pages dev ./dist --r2=THEMES


✘ [ERROR] Unknown argument: r2

jjjrmy

J

jjjrmy•8/19/22, 12:46 PM

wrangler 2.0.24 (update available 2.0.26)

jjjrmy

J

jjjrmy•8/19/22, 12:46 PM

I just upgraded to .26 and it seems to work

jjjrmy

J

jjjrmy•8/19/22, 1:19 PM

when running that command though, I'm still not able to access my R2 instance

jjjrmy

J

jjjrmy•8/19/22, 1:19 PM

Token Permissions:

Scope (Access)
- account (read)
- user (read)
- workers (write)
- workers_kv (write)
- workers_routes (write)
- workers_scripts (write)
- workers_tail (read)
- pages (write)
- zone (read)
- offline_access

Scope (Access)
- account (read)
- user (read)
- workers (write)
- workers_kv (write)
- workers_routes (write)
- workers_scripts (write)
- workers_tail (read)
- pages (write)
- zone (read)
- offline_access

jjjrmy

J

jjjrmy•8/19/22, 1:20 PM

do I need to re-auth to access R2?

Walshy

W

Walshy•8/19/22, 1:22 PM

It's local dev not remote dev so it doesn't have access to your R2 bucket

jjjrmy

J

jjjrmy•8/19/22, 1:22 PM

https://developers.cloudflare.com/pages/platform/functions#using-r2-buckets-locally

Functions (beta) · Cloudflare Pages docs

Documentation for Cloudflare Pages, the best way to deploy your static and JAMstack sites

Functions (beta) · Cloudflare Pages docs

jjjrmy

J

jjjrmy•8/19/22, 1:22 PM

While developing locally, you can interact with an R2 bucket by adding --r2=<BINDING> to your run command. For example, if your bucket is bound to BUCKET, you can access this bucket in local dev by running npx wrangler pages dev dist --r2=BUCKET.

While developing locally, you can interact with an R2 bucket by adding --r2=<BINDING> to your run command. For example, if your bucket is bound to BUCKET, you can access this bucket in local dev by running npx wrangler pages dev dist --r2=BUCKET.

jjjrmy

J

jjjrmy•8/19/22, 1:23 PM

so what do I do?

jjjrmy

J

jjjrmy•8/19/22, 1:26 PM

so then I have to make a worker that makes the R2 accessible

jjjrmy

J

jjjrmy•8/19/22, 1:26 PM

your way seems easiest

jjjrmy

J

jjjrmy•8/19/22, 1:28 PM

but this is not the same case as KV?

jjjrmy

J

jjjrmy•8/19/22, 1:28 PM

because my KV seems to be working fine

Tilon

T

Tilon•8/19/22, 9:25 PM

Does „wrangler dev —local“ with service bindings work for anyone? In the console it says that the local worker is successfully connected to the live service binding, so it looks like it „should“ work. However when the worker tried to access the service, it throws „NAME_OF_SERVICE_BINDING is undefined“

Tilon

TTilon Does „wrangler dev —local“ with service bindings work for anyone? In the console...

TheSunSide

T

TheSunSide•8/19/22, 9:26 PM

Are you using experimental_services(old) instead of services ? Did you specify the Miniflare.mount?

TheSunSide

TTheSunSide Are you using experimental_services(old) instead of services ? Did you specify t...

Tilon

T

Tilon•8/19/22, 9:27 PM

I only use [[services]] in the wrangler.toml

Tilon

TTilon I only use [[services]] in the wrangler.toml

TheSunSide

T

TheSunSide•8/19/22, 9:28 PM

You need to define [miniflare.mounts] so your local env knows where to fetch those workers

TheSunSide

T

TheSunSide•8/19/22, 9:28 PM

I'm using miniflare directly, but it should be similar

Tilon

T

Tilon•8/19/22, 9:29 PM

Thx, I will try that

Tilon

T

Tilon•8/19/22, 9:31 PM

Ignored: "miniflare":
Wrangler does not use configuration in the miniflareminiflare section. Unless you are using Miniflare
directly you can remove this section.

Tilon

T

Tilon•8/19/22, 9:32 PM

Too bad, looks like there is a difference between wrangler local and „pure“ miniflare

TheSunSide

T

TheSunSide•8/19/22, 9:38 PM

▲ [WARNING] This worker is bound to live services: MAIL_FETCH (mail@local), LOGGER_SERVER (logger@local)

local worker: Error: ⎔ Service bindings are not yet supported in local mode.

TheSunSide

T

TheSunSide•8/19/22, 9:38 PM

Might need to wait for wrangler to do it

TheSunSide

T

TheSunSide•8/19/22, 9:38 PM

If you want true "local"

tacomilkshake

T

tacomilkshake•8/19/22, 9:42 PM

New Wrangler dev defaults to 0.0.0.0 so I added [dev] ip = '127.0.0.1' to wrangler.toml. wrangler dev doesn't use that config and remains at 0.0.0.0. Seems like a bug, ya?

Original message was deleted

tacomilkshake

T

tacomilkshake•8/19/22, 10:01 PM

https://github.com/cloudflare/wrangler2/issues/1714

tacomilkshake

T

tacomilkshake•8/19/22, 10:29 PM

Having another very weird issue with Wrangler dev on two devices (Mac + Ubuntu):

npx wrangler init my-worker
cd my-worker/
npx wrangler dev --ip 127.0.0.1

npx wrangler init my-worker
cd my-worker/
npx wrangler dev --ip 127.0.0.1

curl localhost:8787 works

npx wrangler init my-worker
cd my-worker/
npx wrangler secret put TEST
npx wrangler dev --ip 127.0.0.1

npx wrangler init my-worker
cd my-worker/
npx wrangler secret put TEST
npx wrangler dev --ip 127.0.0.1

curl localhost:8787 no longer works -- it just hangs.

Basically, adding an environment variable to any new worker breaks wrangler dev.

Original message was deleted

tacomilkshake

T

tacomilkshake•8/19/22, 10:30 PM

Ah ha, thanks! Kinda glad it's not just me. I was losing my mind!

Original message was deleted

tacomilkshake

T

tacomilkshake•8/19/22, 10:31 PM

ooh, didn't know that. thanks!

kian

K

kian•8/19/22, 10:37 PM

hidden deep under the config code dump https://developers.cloudflare.com/workers/wrangler/configuration/#local-environments

kian

K

kian•8/19/22, 10:37 PM

notlikecatgoogly

kian

K

kian•8/19/22, 10:37 PM

the new one should make it easier imo - https://kian-wrangler-configuration.cloudflare-docs-github.pages.dev/workers/wrangler/configuration/#local-development-settings

kian

K

kian•8/19/22, 10:37 PM

feedback is welcome

TheSunSide

TTheSunSide ▲ [WARNING] This worker is bound to live services: MAIL_FETCH (mail@local), LOGG...

Tilon

T

Tilon•8/19/22, 11:05 PM

Yeah, the thing is that it says for me:
„Support for service bindings in local mode is experimental and may change.“

which sounded like it „could“ work with the latest Wrangler version. I was just curious if it is actually working for anybody.

Tilon

TTilon Yeah, the thing is that it says for me: „Support for service bindings in local m...

TheSunSide

T

TheSunSide•8/19/22, 11:15 PM

https://github.com/cloudflare/wrangler2/pull/1503 might help, not quite sure how to do it

GitHub

feat: zero config multiworker development (local mode) by threepoin...

Preamble: Typically, a Worker has been the unit of a javascript project on our platform. Any logic that you need, you fit into one worker, ~ 1MB of javascript and bindings. If you wanted to deploy ...

feat: zero config multiworker development (local mode) by threepoin...

TheSunSide

TTheSunSide https://github.com/cloudflare/wrangler2/pull/1503 might help, not quite sure how...

Tilon

T

Tilon•8/19/22, 11:31 PM

Thx, I am checking it out

James

J

James•8/21/22, 3:40 PM

Workers Sites does work well with Wrangler 2 fwiw, if you'd prefer to just do that

Scope (Access)
- account (read)
- user (read)
- workers (write)
- workers_kv (write)
- workers_routes (write)
- workers_scripts (write)
- workers_tail (read)
- pages (write)
- zone (read)
- offline_access

Scope (Access)
- account (read)
- user (read)
- workers (write)
- workers_kv (write)
- workers_routes (write)
- workers_scripts (write)
- workers_tail (read)
- pages (write)
- zone (read)
- offline_access

While developing locally, you can interact with an R2 bucket by adding --r2=<BINDING> to your run command. For example, if your bucket is bound to BUCKET, you can access this bucket in local dev by running npx wrangler pages dev dist --r2=BUCKET.

While developing locally, you can interact with an R2 bucket by adding --r2=<BINDING> to your run command. For example, if your bucket is bound to BUCKET, you can access this bucket in local dev by running npx wrangler pages dev dist --r2=BUCKET.