Cloudflare Developers•11mo ago

I don't think we've changed that but let me check

WWalshy I don't think we've changed that but let me check

Aríadust•1/31/25, 3:09 PM

Saw the new release and it fixed the issue. Thank you very much for the quick fix.

WalshyOP•1/31/25, 3:21 PM

Ah perfect was just coming to say it's fixed. Thank you for the report! Sorry for the issue!

Xpertfxglobal•1/31/25, 3:21 PM

Hello

nejc•1/31/25, 10:41 PM

hi all, not sure who is handling github actions, but would it be possible to merge this PR for github actions https://github.com/cloudflare/wrangler-action/pull/348

GitHub

Fix: set deployment-url for "versions upload" command by gferreri ·...

Fixes #343
Simply extend the check to pull deployment-url from stdout if the command is versions upload.

nejc•1/31/25, 10:41 PM

versions are not returning preview url

nejc•2/4/25, 10:26 AM

@Edmund Hung would it be possible to merge this one https://github.com/cloudflare/wrangler-action/pull/348. It would help a lot in our CI/CD flow as right now we can't get staging url. Thank you

nejc•2/4/25, 10:27 AM

if I can help in any way with PR just let me know

EEdmund Hung I have forwarded it to the team. It seems like the PR itself might not be enough...

nejc•2/4/25, 4:00 PM

awesome, thank you for the help. Sadly our CI/CD is currenlty broken because of it as we switched to versions, which is a great thing for previews

verdverm.com•2/4/25, 9:53 PM

Is this a good change to get help with

wrangler

wrangler

and

@opennextjs/cloudflare

@opennextjs/cloudflare

issues?
(the latter looks to be a project headed up by cloudflare employees)

James•2/4/25, 9:56 PM

the opennext discord is generally recommend for support there

zwily•2/6/25, 4:51 AM

i'm trying to

wrangler d1 migrations list letsapply-db --remote

wrangler d1 migrations list letsapply-db --remote

and wrangler is just dying with an exit code of "1" (no text). any suggestions on how to debug?

�

😈 Donkey 💫•2/6/25, 8:50 AM

✘ [ERROR] A request to the Cloudflare API (/accounts/xxx/workers/scripts/xxx/versions) failed.

An unknown error has occurred. If this error persists, please file a report in the workers-sdk
GitHub repository (https://github.com/cloudflare/workers-sdk/issues) or reach out to your account
team. [code: 10002]

�

😈 Donkey 💫•2/6/25, 8:50 AM

one of my workers dead, and cannot deploy

�

😈 Donkey 💫•2/6/25, 8:52 AM

oops, it's binding to R2 actually

Jokcy•2/6/25, 9:06 AM

Hi team, I have worker A and service binding worker B, now I'm trying to develop locally, here is the problem how can I migration to the d1 binding from worker B when developing worker A?

JJokcy Hi team, I have worker A and service binding worker B, now I'm trying to develop...

Jacob Marshall•2/9/25, 3:56 AM

I recently ran into a similar issue (sharing resources between workers) and I believe the solution is to use

wrangler dev

wrangler dev

with multiple configuration files.

wrangler dev

wrangler dev

can now run multiple workers at once and will save the state for each worker in the same

.wrangler

.wrangler

folder on disk - meaning if they point to the same D1 or KV resource (for example), they will point to the same data. The first

wrangler.toml

wrangler.toml

wrangler.json(c)

wrangler.json(c)

file is the "main" worker and will be the one that accepts the incoming HTTP requests. So you basically have to create a new worker that's used locally to help route to your other workers if you have multiple that need to accept incoming HTTP requests. The command you want will look something like this:

wrangler dev -c ./dev-worker/wrangler.jsonc -c ./worker1/wrangler.jsonc -c ./worker2/wrangler.jsonc

wrangler dev -c ./dev-worker/wrangler.jsonc -c ./worker1/wrangler.jsonc -c ./worker2/wrangler.jsonc

Jacob Marshall•2/9/25, 3:59 AM

Also, because the location of the SQLite database locally isn't stored in the same place anymore, you'll have to update your migration command to point to the new location, for example:

wrangler d1 migrations apply d1-db --local --persist-to ./dev-worker/.wrangler/state

wrangler d1 migrations apply d1-db --local --persist-to ./dev-worker/.wrangler/state

itsjxck-io•2/11/25, 8:56 AM

Anyone got good examples of using wrangler in github actions to create branch PR preview deployments?

Iitsjxck-io Anyone got good examples of using wrangler in github actions to create branch PR...

nejc•2/11/25, 2:44 PM

name: Wrangler deploy
uses: cloudflare/wrangler-action@v3
with:
accountId:
apiToken:
command: 'versions upload'

bentlegen•2/11/25, 8:02 PM

didn't see anyone post this, but regression in Wrangler 3.108 causing me grief

https://github.com/cloudflare/workers-sdk/issues/8101

GitHub

🐛 BUG: `wrangler secret list --format json` emits non-JSON characte...

Which Cloudflare product(s) does this pertain to? Wrangler What versions are you using? 3.108.0 What operating system and version are you using? Mac Sequoia 15.1.1 Please provide a link to a minima...

Isak•2/12/25, 12:38 PM

Is there a way to disable deployments to the default environment? We only deploy to our named environments (staging and production).

Original message was deleted

Isak•2/12/25, 4:11 PM

Interesting thank you!

Dean•2/13/25, 10:24 PM

is there any way to stop wrangler deploy from overwriting D1 database bindings, etc? keep-vars does not do it.

Yasserius•2/14/25, 1:45 PM

I found a bug in wrangler deploy, where can i report it?

Yasserius•2/14/25, 1:46 PM

the github issues maybe?

WalshyOP•2/14/25, 2:11 PM

github issue is best yep

WalshyOP•2/14/25, 2:11 PM

what's the issue?

WWalshy what's the issue?

Yasserius•2/14/25, 2:24 PM

I just reread the docs and saw that deployment of python apps doesn't work, i have a fastapi app, so let me wait

Yasserius•2/14/25, 2:24 PM

how soon do you think we will get python deployments? in 3 months? do js backends already work?

WalshyOP•2/14/25, 2:26 PM

See https://discord.com/channels/595317990191398933/1224715939581530112/1332045636983459851 for Python package support

and yes, js works

Jacob Marshall•2/15/25, 5:38 AM

Hi, I've run into an issue for a new project I just started working on, that I've run into before (but the solution I implemented wasn't exactly 'ideal'), and I was wondering if there is an official workaround now. Basically if I'm running a worker locally using

wrangler dev

wrangler dev

, and that worker has a route defined (eg.

*.example.com

*.example.com

), when I try to hit the worker locally (on something like

http://something.localhost:8787

http://something.localhost:8787

) the request URL gets rewritten to

http://example.com

http://example.com

no matter what the subdomain is. Effectively making it impossible for me to use subdomains locally with
```
wrangler dev
```
```
wrangler dev
```
. Is there any way of disabling this functionality locally? I totally get why it's there (for non-wildcard routes) but it causes issues with subdomains.

João Castro•2/16/25, 10:02 PM

Are the wrangler.toml validators exported/published anywhere for third party libraries to use?

James•2/16/25, 10:10 PM

I'm not sure if there's any exposed validators code-wise, but they do publish a

config-schema.json

config-schema.json

with

wrangler

wrangler

on npm that you could use to validate with any JSON schema validator.

JJoão Castro Are the wrangler.toml validators exported/published anywhere for third party lib...

Hello, I’m Allie!•2/16/25, 10:20 PM

IIRC too there is some kind of shebang that you can put at the top of the toml file to have it validated. I think it works with the

Even Better TOML

Even Better TOML

extension, but I don’t think it is standard

James•2/16/25, 10:26 PM

#: schema ./node_modules/wrangler/config-schema.json

#: schema ./node_modules/wrangler/config-schema.json

yep

verdverm.com•2/17/25, 4:18 AM

In local dev mode with wrangler, is there a way to run a worker and a durable object.

worker is the main site
durable is a websocket server under /path
This setup works find in production, where I can use worker routes. Is there something similar for local dev? (so it looks like both are under localhost:3000 and I can dev like I prod?

Vverdverm.com In local dev mode with wrangler, is there a way to run a worker and a durable ob...

Hard@Work•2/17/25, 10:12 AM

Not entirely sure I understand what you mean? You can just have the Worker forward requests on

/path

/path

to your DO?

ashutosh•2/17/25, 11:28 AM

I am on v3.109.1 and whenever I try to deploy with wrangler deploy, getting this error:

You are logged in with an API Token. Unset the CLOUDFLARE_API_TOKEN in the environment to log in via OAuth.

You are logged in with an API Token. Unset the CLOUDFLARE_API_TOKEN in the environment to log in via OAuth.

Why can't I deploy with CLOUDFLARE_API_TOKEN ? It used to work fine with older version!

memeFicated2025•2/17/25, 7:54 PM

hi team ! How can we handle very sensetive data like crypto wallet keys in backend using workers ? what is the recommended approach?

HHard@Work Not entirely sure I understand what you mean? You can just have the Worker forwa...

verdverm.com•2/17/25, 8:31 PM

On localhost, where I am developing. I already do that in prod between workers, I need something better on localhost for multiple workers running at the same time

Vverdverm.com On localhost, where I am developing. I already do that in prod between workers, ...

Hello, I’m Allie!•2/17/25, 8:48 PM

Oh, you meant a DO within one Worker and a separate Worker, on the same port?

Hello, I’m Allie!•2/17/25, 8:49 PM

I don’t think you can do that now. Maybe make an issue on workers-sdkworkers-sdk?

HHello, I’m Allie!Oh, you meant a DO within one Worker and a separate Worker, on the same port?

verdverm.com•2/17/25, 8:56 PM

Is it possible to connect two workers on localhost through the binding mechanisms? (This subpath stuff is going away eventually, can move that work forward)

Vverdverm.com Is it possible to connect two workers on localhost through the binding mechanism...

Hello, I’m Allie!•2/17/25, 10:01 PM

Hm… that might work?

HHello, I’m Allie!Hm… that might work?

verdverm.com•2/17/25, 10:07 PM

I recall (maybe) that it was not supported yet, but I was a bit early in my journey to hang the details on prior experience. For now, for the feature I'm working on, http fetch is going to be fine, just have to make the websocket host configurable for dev vs prod.

Actually, I did want the websocket worker to share the D1 & KV with the webapp worker. Is this possible in prod & local dev? (prod seems like an easy yes? while dev seems like it may be an issue because they are in different dirs and running in different wrangler setups?

verdverm.com•2/17/25, 10:08 PM

Maybe using a remote preview environment is the way to handle this in local dev mode?

I don't think we've changed that but let me check

Similar Threads