I don't understand why a worker can't use all the Node.js modules, so what powerful features can he

S

SnowBall•6/5/25, 1:43 PM

hi

T

top kek•6/5/25, 3:38 PM

how can I share the same D1 db (binding) across two apps in a monorepo?

Yyinxingmaiming6409 I don't understand why a worker can't use all the Node.js modules, so what power...

H

Hard@Work•6/5/25, 4:37 PM

The reason is that Workers runs on

workerd

workerd

, not NodeJS. There is a NodeJS compatibility layer, which adds support for some things, but they are inherently two separate things

I

Isaac McFadyen•6/5/25, 5:02 PM

Apart from forwarding requests and writing HTML

There's lots you can do without Node compat, a lot of people make APIs on Workers, and you can access databases now (plus Hyperdrive if you want to speed them up), or use KV for global read-heavy storage, or R2 for blob storage, etc.

HHard@Work The reason is that Workers runs on `workerd`, not NodeJS. There is a NodeJS comp...

Y

yinxingmaiming6409OP•6/6/25, 1:03 AM

At present, the advantage of workers seems to be accessing many CloudFlare services without limiting the frequency, right? Higher frequency than HTTP

Ttop kek how can I share the same D1 db (binding) across two apps in a monorepo?

G

Gravite2090•6/6/25, 11:01 PM

One way is to create the same D1 binding in each app's respective wrangler config file. If you are using local based dev and want both your monorepo workers to share the same data, you can use something like this for your run command(s):
wrangler dev --persist-to ../../.wrangler
where ../../.wrangler is the path to the folder where you want the shared data/state to exist

R

relates•6/7/25, 4:09 AM

hello :wave: is the

--yes

--yes

--yes

--yes bugged with

wrangler rollback

wrangler rollback

wrangler rollback

wrangler rollback ?

It doesn't automatically accepts default, I have to manually enter.

D

Dev•6/7/25, 6:52 AM

I'm experiencing these

Authentication error [code: 10000]

Authentication error [code: 10000]

Authentication error [code: 10000]

Authentication error [code: 10000] a lot lately. If it knows how I'm logged in, then why is it giving me errors. I've tried logging out and logging back in

DDev I'm experiencing these `Authentication error [code: 10000]` a lot lately. If it ...

D

Dev•6/7/25, 7:19 AM

it worked now, dont know why it was giving errors

9

9•6/7/25, 9:11 AM

Hello everyone

I'm having an issue with

wrangler dev --remote

wrangler dev --remote

( or

npx wrangler dev --remote

npx wrangler dev --remote

) in Cloudflare Workers. When I run this command and press 'b' to open the browser, I get redirected from

http://127.0.0.1:8787/

http://127.0.0.1:8787/

http://127.0.0.1:8787/

http://127.0.0.1:8787/ to my production workers.dev URL instead of seeing my development environment.

Terminal shows:

[wrangler:info] GET / 307 Temporary Redirect (14052ms)

[wrangler:info] GET / 307 Temporary Redirect (14052ms)

[wrangler:info] GET / 307 Temporary Redirect (14052ms)

[wrangler:info] GET / 307 Temporary Redirect (14052ms)

I need to use

--remote

--remote

to access my remote D1 database during development, but can't see my dev environment or terminal output.

Wrangler 4.19.1, Node 22.16.0
Config has

preview_urls = true

preview_urls = true

preview_urls = true

preview_urls = true and

workers_dev = true

workers_dev = true

workers_dev = true

workers_dev = true

Any ideas how to fix this? Or anything that I can try differently. The problem happens consistently on every retries. Any help is greatly appreciated!

9

9•6/7/25, 9:14 AM

W

Walshy•6/7/25, 9:53 AM

ty

N

nasso•6/7/25, 6:32 PM

guys i think i am going insane, is there any sane way to delete a local d1 database?

sometimes when prototyping you can get your local db all messed up. i often like fully recreating it and applying the migrations (using

wrangler d1 migrations apply

wrangler d1 migrations apply

)

i added scripts in my

package.json

package.json

like

migrations:apply

migrations:apply

migrations:apply

migrations:apply,

migrations:list

migrations:list

migrations:list

migrations:list,

migrations:gen

migrations:gen

migrations:gen

migrations:gen. how can i make a script that effectively deletes the local db +

migrations:apply

migrations:apply

migrations:apply

migrations:apply??

R

relates•6/8/25, 10:49 AM

do we have command in wrangler for pages rollback? If not, is it planned?

N

nasso•6/9/25, 12:59 PM

okay so you really gotta

rm -rf .wrangler/state

rm -rf .wrangler/state

rm -rf .wrangler/state

rm -rf .wrangler/state
i was hoping there was gonna be a way to get the path to specifically the d1 sqlite file for example but that's good enough for me

N

nasso•6/9/25, 12:59 PM

thank you!

A

ALECKS•6/10/25, 4:15 PM

how do I use wrangler dev to run multiple workers locally at the same time? Say I have:
- auth-svc worker that has a route: ".app.test/auth/"
- api worker with a route: ".app.test/api/"

do I need to handle a proxy in front of each myself, or is there something built into wrangler, or other best practice?

S

Suji•6/10/25, 9:47 PM

Does anyone know how to get the preview url during the build in workers ? (before the version upload)

AALECKS how do I use wrangler dev to run multiple workers locally at the same time? Say ...

S

Silvan•6/10/25, 9:47 PM

well either you just run wrangler dev in both projects or you can also specifcy multiple wrangler files with the -c paramter

T

thipperz•6/10/25, 11:47 PM

I tried to access remote D1 bindings with

wrangler dev

wrangler dev

and the new Mixed Mode, unfortunately all D1 operations seem to timeout. I know that stuff is still WIP but I'm pretty excited for it, it will solve a lot of my headaches with local dev

I

ItsWendell•6/11/25, 9:39 AM

Something odd I keep running into with wrangler authentication (e.g. for deploy) is that sometimes I yolo run

wrangler deploy

wrangler deploy

in my turborepo (it deploys multiple workers in parallel) when I need to hot-fix something, the first time I do this, I get the oauth popup for cloudflare. Now even though I do nothing with that popup, and I just run

deploy

deploy

again, it suddenly does work, even though I haven't approved the oauth2 popup.

My system is generally logged in with wrangler though, so I feel like that first oauth2 pop-up was unnessesary?

A

ALECKS•6/13/25, 6:57 PM

If I have a worker (DASHBOARD) using Vite + local worker, cloudflare-vite-plugin... then I proxy traffic to this worker from another by doing this:

env.DASHBOARD.fetch(request)

env.DASHBOARD.fetch(request)

env.DASHBOARD.fetch(request)

env.DASHBOARD.fetch(request) Should this call behave like a normal http call, and server SPA assets when

not_found_handling: "single-page-application"

not_found_handling: "single-page-application"

not_found_handling: "single-page-application"

not_found_handling: "single-page-application" or does it mean it does a direct RPC call to the local worker and will never return static assets, like you'd get from a regular http call to the worker?

M

mrugesh•6/14/25, 3:49 PM

I just finished migrating a pages project to workers, and I would love to know if there is a way to changes I make on the UI into my wrangler config file. I keep seeing this working about syncing it, but it would be nice to be able to download the config file and swap out the one I have locally/in vcs?

A

ALECKS•6/16/25, 3:29 PM

Not sure if this is a bug or intended behavior. I have a local tail worker that captures logs from all my services. I want to add a simple web ui so I can view logs in the browser. Adding a fetch() method to the worker works fine, but adding an

assets

assets

configuration, even with

run_worker_first: true

run_worker_first: true

run_worker_first: true

run_worker_first: true breaks it, the tail() method is no longer invoked

AALECKS how do I use wrangler dev to run multiple workers locally at the same time? Say ...

M

Marco•6/17/25, 6:42 AM

This works for me: npx wrangler dev -c folder1/wrangler.toml -c folder2/wrangler.toml --persist-to .wrangler/state

sharing the state is necessary if they have any asset in common. by asset i mean R2, D1, Queue, etc

V

veeque•6/17/25, 9:14 AM

what does

--host

--host

actually do?

V

veeque•6/17/25, 9:15 AM

in the dev command

Mmrugesh I just finished migrating a pages project to workers, and I would love to know i...

M

Marco•6/17/25, 9:20 AM

I am not aware of such feature. I run into a similar problem in the past when experimenting and the only way (I know) to fix it is to be patient and experiment - you rally want your toml file to set the config instead of the UI. In my case, it was a matter of making sure I got the bindings and secrets right.

That said, I just tried pasting into ChatGPT a screenshot of the Bindings and it generated a pretty good .toml file

Original message was deleted

V

veeque•6/17/25, 10:28 AM

yea sorry, asked that question when i was losing my mind over something.

i am trying to figure out how wrangler/mini flare look for the service bindings and if there’s a way to have it “networked” rather than via the registry daemon/file

V

veeque•6/17/25, 12:43 PM

in miniflare i can make a service binding on an external machine like so:

import { Miniflare } from "miniflare";

const mf = new Miniflare({
  host: "0.0.0.0",
  port: 3000,
  workers: [
    {
      name: "worker",
      serviceBindings: {
        TEST: {
            // this key here
            external: {
                address: "127.0.0.1:8787"
            }
        }
      },
      modules: true,
      scriptPath:'path/to/worker.js'
    },
  ],
});
await mf.ready

import { Miniflare } from "miniflare";

const mf = new Miniflare({
  host: "0.0.0.0",
  port: 3000,
  workers: [
    {
      name: "worker",
      serviceBindings: {
        TEST: {
            // this key here
            external: {
                address: "127.0.0.1:8787"
            }
        }
      },
      modules: true,
      scriptPath:'path/to/worker.js'
    },
  ],
});
await mf.ready

import { Miniflare } from "miniflare";

const mf = new Miniflare({
  host: "0.0.0.0",
  port: 3000,
  workers: [
    {
      name: "worker",
      serviceBindings: {
        TEST: {
            // this key here
            external: {
                address: "127.0.0.1:8787"
            }
        }
      },
      modules: true,
      scriptPath:'path/to/worker.js'
    },
  ],
});
await mf.ready

import { Miniflare } from "miniflare";

const mf = new Miniflare({
  host: "0.0.0.0",
  port: 3000,
  workers: [
    {
      name: "worker",
      serviceBindings: {
        TEST: {
            // this key here
            external: {
                address: "127.0.0.1:8787"
            }
        }
      },
      modules: true,
      scriptPath:'path/to/worker.js'
    },
  ],
});
await mf.ready

i doubt this is currently doable with wrangler (or by setting it in wrangler.jsonc), what would be the reason?

MMarco This works for me: npx wrangler dev -c folder1/wrangler.toml -c folder2/wrangler...

A

ALECKS•6/17/25, 12:49 PM

By asset I meant especifically an

"assets"

"assets"

"assets"

"assets" configuration, a folder of static files to be served, like an html file or images, NOT other bindings

C

crgeary•6/17/25, 7:20 PM

When setting the

--tag

--tag

--tag

--tag on

wrangler versions upload

wrangler versions upload

wrangler versions upload

wrangler versions upload has anyone had issues with it not being set on vite projects? I'm not sure if I am doing something incorrectly, or if it's a bug in the wrangler CLI.

It works fine for me on a non vite project, this is my command:

pnpm --filter @company/app exec \
  wrangler versions upload --tag "commit-${GITHUB_SHA::7}"

pnpm --filter @company/app exec \
  wrangler versions upload --tag "commit-${GITHUB_SHA::7}"

pnpm --filter @company/app exec \
  wrangler versions upload --tag "commit-${GITHUB_SHA::7}"

pnpm --filter @company/app exec \
  wrangler versions upload --tag "commit-${GITHUB_SHA::7}"

The same is also true for

--message

--message

--message

--message

A

ALECKS•6/19/25, 12:42 AM

does this new Remote Binding work with queues?

A

ALECKS•6/19/25, 1:20 AM

  - Unexpected fields found in queues.consumers[0] field: "experimental_remote"

- Unexpected fields found in queues.consumers[0] field: "experimental_remote"

  - Unexpected fields found in queues.consumers[0] field: "experimental_remote"

- Unexpected fields found in queues.consumers[0] field: "experimental_remote" in the consumer on start..

C

crgeary•6/22/25, 1:52 PM

Am I correct in thinking there is no way to add new secrets and code changes at the same time with Wrangler? I'd need to do 2 individual deployments to make code & secret changes?

J

James•6/22/25, 2:25 PM

That’s true, yep. You can do multiple secrets via the bulk functionality, but if you want to push code changes as well, that’ll be a separate command

JJames That’s true, yep. You can do multiple secrets via the bulk functionality, but if...

C

crgeary•6/22/25, 2:31 PM

I see, thanks!

R

Ricky U•6/24/25, 2:53 PM

Need some help with using Secrets Store (not secrets) locally using npx wrangler dev.. even with the --remote flag it wont work..-- how do you use secrets store locally, or rather how do you fall back to local .evv vars?

Y

yawnxyz•6/25/25, 4:55 PM

for those trying out wrangler + containers, did you see this

You don't have 'containers:write' in your list of scopes

You don't have 'containers:write' in your list of scopes

You don't have 'containers:write' in your list of scopes

You don't have 'containers:write' in your list of scopes

edit: just update wrangler

S

SuperHelpflare•6/25/25, 4:56 PM

Please do not post your question in multiple channels/post it multiple times per the rules at #

welcome-and-rules. It creates confusion for people trying to help you and doesn't get your issue or question solved any faster.

M

Metalstorm•6/25/25, 4:56 PM

When trying to use .env for authentication, i am getting the following error:

You are logged in with an API Token. Unable to retrieve email for this user. Are you missing the

You are logged in with an API Token. Unable to retrieve email for this user. Are you missing the

You are logged in with an API Token. Unable to retrieve email for this user. Are you missing the

You are logged in with an API Token. Unable to retrieve email for this user. Are you missing the User->User Details->Read

 permission?

permission?

 permission?

permission?

I have checked the token and it has

All users - Memberships:Read, User Details:Read

All users - Memberships:Read, User Details:Read

All users - Memberships:Read, User Details:Read

All users - Memberships:Read, User Details:Read

it is able to print out my

account name

account name

account name

account name and

account id

account id

account id

account id and these match what i expect. (I cannot use

wrangler login

wrangler login

)

S

sallomendo•6/25/25, 9:19 PM

Are RPC on Worker Enpoints not supported yet with experimental remote bindings? We are getting

TypeError: The RPC receiver does not implement the method

TypeError: The RPC receiver does not implement the method

TypeError: The RPC receiver does not implement the method

TypeError: The RPC receiver does not implement the method errors while trying to call methods on a remote binding.

F

Fedi4Life•6/26/25, 1:29 AM

My cloudflare deployment with the @sveltejs/adapter-cloudflare v7.0.4 just started failing with

Error: The provided Wrangler config main field
  (/Users/<username>/Developer/<appname>/.svelte-kit/cloudflare/_worker.js) doesn't point to an
  existing file

Error: The provided Wrangler config main field
  (/Users/<username>/Developer/<appname>/.svelte-kit/cloudflare/_worker.js) doesn't point to an
  existing file

Error: The provided Wrangler config main field
  (/Users/<username>/Developer/<appname>/.svelte-kit/cloudflare/_worker.js) doesn't point to an
  existing file

Error: The provided Wrangler config main field
  (/Users/<username>/Developer/<appname>/.svelte-kit/cloudflare/_worker.js) doesn't point to an
  existing file

That directory and file used to be there with previous versions of the adapter, but now the generated directory structure is

.../.svelte-kit/generated/client/app.js

.../.svelte-kit/generated/client/app.js

.../.svelte-kit/generated/client/app.js

.../.svelte-kit/generated/client/app.js and

.../.svelte-kit/generated/server/internal.js

.../.svelte-kit/generated/server/internal.js

.../.svelte-kit/generated/server/internal.js

.../.svelte-kit/generated/server/internal.js

The associated wrangler.toml file that had been working has this for the app entry point:

main = ".svelte-kit/cloudflare/_worker.js"

main = ".svelte-kit/cloudflare/_worker.js"

main = ".svelte-kit/cloudflare/_worker.js"

main = ".svelte-kit/cloudflare/_worker.js"

This seems to have snowballed from trying to add some node native functions to my app and had to upgrade serveral packages to end up here. This may be a user issue, or Wrangler/Cloudflare, but this adapter sits between Cloudflare and SvelteKit so it seems a good place to ask for help.

Thanks

K

kchro3•6/26/25, 10:50 PM

Can I get help with this local remote-binding?

[wrangler:info] Ready on http://localhost:8787
⎔ Starting local server...
▲ [WARNING] workerd/api/r2-rpc.c++:122: warning: R2 error response does not contain the CF-R2-Error header.; response.statusCode = 500

✘ [ERROR] [Error: get: Unspecified error (0)]

[wrangler:info] Ready on http://localhost:8787
⎔ Starting local server...
▲ [WARNING] workerd/api/r2-rpc.c++:122: warning: R2 error response does not contain the CF-R2-Error header.; response.statusCode = 500

✘ [ERROR] [Error: get: Unspecified error (0)]

[wrangler:info] Ready on http://localhost:8787
⎔ Starting local server...
▲ [WARNING] workerd/api/r2-rpc.c++:122: warning: R2 error response does not contain the CF-R2-Error header.; response.statusCode = 500

✘ [ERROR] [Error: get: Unspecified error (0)]

[wrangler:info] Ready on http://localhost:8787
⎔ Starting local server...
▲ [WARNING] workerd/api/r2-rpc.c++:122: warning: R2 error response does not contain the CF-R2-Error header.; response.statusCode = 500

✘ [ERROR] [Error: get: Unspecified error (0)]

using an R2 remote binding locally

Kkchro3 Can I get help with this local remote-binding? ``` [wrangler:info] Ready on http...

A

Amber•6/26/25, 11:09 PM

Yes I can help you

AAmber Yes I can help you

K

kchro3•6/26/25, 11:20 PM

Hey Amber, thank you. It looks like it's failing when I call R2 like this:

const payload = await this.bucket.get(key);

but it works in prod

K

kchro3•6/26/25, 11:25 PM

my wrangler.toml looks like this:

name = "..."
main = "index.ts"
compatibility_date = "2025-06-26"
compatibility_flags = ["nodejs_compat"]

[[r2_buckets]]
binding = "..."
bucket_name = "..."
preview_bucket_name = "..."
experimental_remote = true

name = "..."
main = "index.ts"
compatibility_date = "2025-06-26"
compatibility_flags = ["nodejs_compat"]

[[r2_buckets]]
binding = "..."
bucket_name = "..."
preview_bucket_name = "..."
experimental_remote = true

name = "..."
main = "index.ts"
compatibility_date = "2025-06-26"
compatibility_flags = ["nodejs_compat"]

[[r2_buckets]]
binding = "..."
bucket_name = "..."
preview_bucket_name = "..."
experimental_remote = true

name = "..."
main = "index.ts"
compatibility_date = "2025-06-26"
compatibility_flags = ["nodejs_compat"]

[[r2_buckets]]
binding = "..."
bucket_name = "..."
preview_bucket_name = "..."
experimental_remote = true

J

Jay•6/29/25, 3:46 PM

I’m getting an error when I try to create a d1 database. I get the error saying that I don’t have Super Administrator, I’ve checked and I do. How do I go by fixing this?

I don't understand why a worker can't use all the Node.js modules, so what powerful features can he

Similar Threads

Similar Threads

Similar Threads