- Cloudflare Developers

D

Divyendu•7/4/24, 3:38 PM

Can I refer to env vars in wrangler.toml? I am setting up inngest with Cloudflare and need to set INNGEST_SIGNING_KEY, technically that's a "secret" but setting it via

wrangler secret put INNGEST_SIGNING_KEY

wrangler secret put INNGEST_SIGNING_KEY

wrangler secret put INNGEST_SIGNING_KEY

wrangler secret put INNGEST_SIGNING_KEY doesn't make it available in the "environment variables", inngest sync fails and to put it in environment variables, I need to add it to wrangler.toml as "plain text" and deploy.

Aaj Click to see attachment

W

Walshy•7/4/24, 3:40 PM

everything in wrangler toml is safe to share fwiw but regardless, assuming that's at the top of the file - seems fine but i'd need the whole thing to say for sure

A

ajOP•7/4/24, 3:41 PM

That is the whole thing.. Thanks anyway :)

S

sadsciencee•7/5/24, 6:38 AM

is it possible to still use .dev.vars localy while using wrangler.toml to manages pages deployment? not seeing anything in the docs and when I run pages dev it just defaults to the 'preview' environment (which is more of a staging env for me, not meant for local dev)

A

Arpit•7/5/24, 7:24 AM

Hey all, I need help, I am not able to run any wrangler project, not even a fresh template, all of them giving this error

PS D:\others\durable-objects-template> wrangler dev

 ⛅️ wrangler 3.63.1
-------------------

Your worker has access to the following bindings:
- Durable Objects:
  - COUNTER: Counter
⎔ Starting local server...
╭─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ [b] open a browser, [d] open Devtools, [l] turn off local mode, [c] clear console, [x] to exit
╰─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
C:\Users\user\AppData\Roaming\npm\node_modules\wrangler\wrangler-dist\cli.js:29765
            throw a;
            ^

MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.
    at #assembleAndUpdateConfig (C:\Users\user\AppData\Roaming\npm\node_modules\wrangler\node_modules\miniflare\dist\src\index.js:9178:13)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Mutex.runWith (C:\Users\user\AppData\Roaming\npm\node_modules\wrangler\node_modules\miniflare\dist\src\index.js:3521:16) {
  code: 'ERR_RUNTIME_FAILURE',
  cause: undefined
}

Node.js v20.14.0

PS D:\others\durable-objects-template> wrangler dev

 ⛅️ wrangler 3.63.1
-------------------

Your worker has access to the following bindings:
- Durable Objects:
  - COUNTER: Counter
⎔ Starting local server...
╭─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ [b] open a browser, [d] open Devtools, [l] turn off local mode, [c] clear console, [x] to exit
╰─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
C:\Users\user\AppData\Roaming\npm\node_modules\wrangler\wrangler-dist\cli.js:29765
            throw a;
            ^

MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.
    at #assembleAndUpdateConfig (C:\Users\user\AppData\Roaming\npm\node_modules\wrangler\node_modules\miniflare\dist\src\index.js:9178:13)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Mutex.runWith (C:\Users\user\AppData\Roaming\npm\node_modules\wrangler\node_modules\miniflare\dist\src\index.js:3521:16) {
  code: 'ERR_RUNTIME_FAILURE',
  cause: undefined
}

Node.js v20.14.0

PS D:\others\durable-objects-template> wrangler dev

 ⛅️ wrangler 3.63.1
-------------------

Your worker has access to the following bindings:
- Durable Objects:
  - COUNTER: Counter
⎔ Starting local server...
╭─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ [b] open a browser, [d] open Devtools, [l] turn off local mode, [c] clear console, [x] to exit
╰─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
C:\Users\user\AppData\Roaming\npm\node_modules\wrangler\wrangler-dist\cli.js:29765
            throw a;
            ^

MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.
    at #assembleAndUpdateConfig (C:\Users\user\AppData\Roaming\npm\node_modules\wrangler\node_modules\miniflare\dist\src\index.js:9178:13)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Mutex.runWith (C:\Users\user\AppData\Roaming\npm\node_modules\wrangler\node_modules\miniflare\dist\src\index.js:3521:16) {
  code: 'ERR_RUNTIME_FAILURE',
  cause: undefined
}

Node.js v20.14.0

PS D:\others\durable-objects-template> wrangler dev

 ⛅️ wrangler 3.63.1
-------------------

Your worker has access to the following bindings:
- Durable Objects:
  - COUNTER: Counter
⎔ Starting local server...
╭─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ [b] open a browser, [d] open Devtools, [l] turn off local mode, [c] clear console, [x] to exit
╰─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
C:\Users\user\AppData\Roaming\npm\node_modules\wrangler\wrangler-dist\cli.js:29765
            throw a;
            ^

MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.
    at #assembleAndUpdateConfig (C:\Users\user\AppData\Roaming\npm\node_modules\wrangler\node_modules\miniflare\dist\src\index.js:9178:13)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Mutex.runWith (C:\Users\user\AppData\Roaming\npm\node_modules\wrangler\node_modules\miniflare\dist\src\index.js:3521:16) {
  code: 'ERR_RUNTIME_FAILURE',
  cause: undefined
}

Node.js v20.14.0

A

Arpit•7/5/24, 7:25 AM

what am i missing ... ?

R

Royal•7/5/24, 8:57 AM

Hello, I have a question about running

wrangler dev --remote

wrangler dev --remote

is it possible to only specify to run R2 remotely but other service to be run locally?

Original message was deleted

R

Royal•7/5/24, 9:26 AM

Thank you for the clarifications

J

João Castro•7/7/24, 2:22 AM

I'm trying to use a service binding from a Cloudflare Pages project to a Worker, and the binding does not work locally if the Pages dev server is started before the Worker. From what i read in the docs, this doesn't seem to be the intended behavior

M

MadManick•7/7/24, 8:29 AM

Hello, I have a question with environments and wrangler.

I need to configure a d1 database for preview and production environments separately, but want to use the same binding name for both. That way the code would be the same but connected database would be different.

Right now, I am trying something like this

[[d1_databases]]
binding = "DB"
database_name = "name"
database_id = "<uuid>"
migrations_dir = "./migrations"

[env.preview]
[[d1_databases]]
binding = "DB"
database_name = "name-preview"
database_id = "<uuid>"
migrations_dir = "./migrations"

[[d1_databases]]
binding = "DB"
database_name = "name"
database_id = "<uuid>"
migrations_dir = "./migrations"

[env.preview]
[[d1_databases]]
binding = "DB"
database_name = "name-preview"
database_id = "<uuid>"
migrations_dir = "./migrations"

[[d1_databases]]
binding = "DB"
database_name = "name"
database_id = "<uuid>"
migrations_dir = "./migrations"

[env.preview]
[[d1_databases]]
binding = "DB"
database_name = "name-preview"
database_id = "<uuid>"
migrations_dir = "./migrations"

[[d1_databases]]
binding = "DB"
database_name = "name"
database_id = "<uuid>"
migrations_dir = "./migrations"

[env.preview]
[[d1_databases]]
binding = "DB"
database_name = "name-preview"
database_id = "<uuid>"
migrations_dir = "./migrations"

But this errors out while deploying with "Failed to publish your Function. Got error: the binding name 'DB' cannot be used more than once". Is there a way to do this?

Original message was deleted

M

MadManick•7/7/24, 8:58 AM

Thanks! That worked!

Original message was deleted

J

João Castro•7/7/24, 8:00 PM

Then how are circular dependencies handled? Its not possible to run two workers that have Service Bindings to each other locally?

J

João Castro•7/7/24, 8:04 PM

Sounds good! I'll give it a go soon

C

cosbgn•7/8/24, 6:55 AM

My app fails after I save something and the dev server rebuilds with:

 ERROR  [unhandledRejection] connect ECONNREFUSED 127.0.0.1:63231     8:51:07 AM

 ERROR  [unhandledRejection] connect ECONNREFUSED 127.0.0.1:63231     8:51:07 AM

 ERROR  [unhandledRejection] connect ECONNREFUSED 127.0.0.1:63231     8:51:07 AM

 ERROR  [unhandledRejection] connect ECONNREFUSED 127.0.0.1:63231     8:51:07 AM

I'm trying to understand which service causes this. Could it be

getPlatformProxy()

getPlatformProxy()

getPlatformProxy()

getPlatformProxy() of wrangler?

R

rampatra•7/8/24, 11:49 AM

For those who use nextjs and d1 database, how's your setup like? Do you have the db logic inside the one nextjs app or do you have 2 separate apps -- nextjs and wrangler generated standalone app for db logic -- deployed as 2 different workers on cloudflare?

AArpit Hey all, I need help, I am not able to run any wrangler project, not even a fres...

M

Mayuresh Choudhary•7/8/24, 2:40 PM

downgrade your Wrangler version to 3.61.0 or less
and use wrangler dev (or wrangler commands)

B

Ben•7/8/24, 5:04 PM

is there a way to have one "global" wrangler.toml file? I have a monorepo with a bunch of packages that need to access the same db, and I am trying to work through the best way to do that.

Bbsam75 Anyone know what im doing wrong? ive been trying to get it to work for a while n...

K

kian•7/8/24, 10:19 PM

Miniflare is a standalone library, you can't run it in

wrangler dev

wrangler dev

wrangler dev

wrangler dev if that's what you're trying to do?

K

kian•7/8/24, 10:19 PM

wrangler dev

wrangler dev

wrangler dev

wrangler dev is Miniflare under the hood, and runs Workers

J

James•7/8/24, 10:23 PM

What's the

wrangler

wrangler

wrangler

wrangler version in your

package.json

package.json

?

J

James•7/8/24, 10:24 PM

npx

npx

npx

npx likes to be annoying with caching. What happens if you run

npx wrangler@3.63.1 dev

npx wrangler@3.63.1 dev

npx wrangler@3.63.1 dev

npx wrangler@3.63.1 dev

J

James•7/8/24, 10:25 PM

If you're creating a new project, I'd definitely recommend

npm create cloudflare@latest

npm create cloudflare@latest

npm create cloudflare@latest

npm create cloudflare@latest: https://developers.cloudflare.com/workers/get-started/guide/

Cloudflare Docs

Get started - CLI · Cloudflare Workers docs

Set up and deploy your first Worker with Wrangler, the Cloudflare Developer Platform CLI.

J

James•7/8/24, 10:26 PM

Can you share your repository/config?

J

James•7/8/24, 10:26 PM

If this is a new project, I'd again heavily encourage you to start over with

npm create cloudflare@latest

npm create cloudflare@latest

npm create cloudflare@latest

npm create cloudflare@latest. That'll ensure you get all the right dependencies and things

J

James•7/8/24, 10:31 PM

That should be fine. Can you share the script you're trying to run and a full error log please?

J

James•7/8/24, 10:32 PM

Is your intent to use

miniflare

miniflare

miniflare

miniflare directly for some specific purpose, or just run a script on Cloudflare Workers?

J

James•7/8/24, 10:32 PM

wrangler dev

wrangler dev

wrangler dev

wrangler dev is not how you'd invoke something like that - the miniflare API runs via

node

node

node

node, but is not generally something 99% of users will need to touch

J

James•7/8/24, 10:33 PM

If you

npm create cloudflare@latest

npm create cloudflare@latest

npm create cloudflare@latest

npm create cloudflare@latest, it'll give you a basic foundation script and a dev script you can run via

npm run dev

npm run dev

npm run dev

npm run dev, etc.

J

James•7/8/24, 10:34 PM

You can't run

Miniflare

Miniflare

Miniflare

Miniflare like that via

wrangler dev

wrangler dev

wrangler dev

wrangler dev. The miniflare APIs are intended for much lower programattic access and is what

wrangler

wrangler

wrangler

wrangler uses under the hoodo

J

James•7/8/24, 10:35 PM

You could use miniflare for that like what you have, but you'd run it via

node

node

node

node and not

wrangler

wrangler

wrangler

wrangler. But if this is for some test suite, the vitest integration is going to be your best option: https://developers.cloudflare.com/workers/testing/vitest-integration/

J

James•7/8/24, 10:37 PM

Yeah, that won't work, miniflare doesn't have a CLI anymore. And your script isn't a workers script that works this way.

J

James•7/8/24, 10:38 PM

You could probably run your code via

node

node

node

node directly

Similar Threads