but this is definitely a really awkward aspect of developing with workers

Ddan but this is definitely a really awkward aspect of developing with workers

D

DaniFoldi•3/27/25, 5:30 PM

Agreed

J

JacobMGEvans•3/28/25, 2:12 AM

I am about to get REAL into Durable Objects, be pepared for an onslaught of stupid questions

V

Vlady•3/29/25, 1:10 AM

Y'all, my build used to work with wrangler 3, but not with v4. Why is wrangler expecting the config to be in the build folder when I build my app and run

wrangler dev

wrangler dev

?

There is a deploy configuration at ".wrangler/deploy/config.json".

  But the redirected configuration path it points to, "build/server/wrangler.json", does not exist.

There is a deploy configuration at ".wrangler/deploy/config.json".

  But the redirected configuration path it points to, "build/server/wrangler.json", does not exist.

There is a deploy configuration at ".wrangler/deploy/config.json".

  But the redirected configuration path it points to, "build/server/wrangler.json", does not exist.

There is a deploy configuration at ".wrangler/deploy/config.json".

  But the redirected configuration path it points to, "build/server/wrangler.json", does not exist.

wrangler.toml

compatibility_date = "2025-02-10"
compatibility_flags = ["nodejs_compat"]
assets = { directory = "./build/client" }
main = './src/entry.worker.ts'

compatibility_date = "2025-02-10"
compatibility_flags = ["nodejs_compat"]
assets = { directory = "./build/client" }
main = './src/entry.worker.ts'

compatibility_date = "2025-02-10"
compatibility_flags = ["nodejs_compat"]
assets = { directory = "./build/client" }
main = './src/entry.worker.ts'

compatibility_date = "2025-02-10"
compatibility_flags = ["nodejs_compat"]
assets = { directory = "./build/client" }
main = './src/entry.worker.ts'

I'm running my

yarn preview

yarn preview

yarn preview

yarn preview script, here's how it's defined in package.json

 "preview": "yarn build && wrangler dev",
 "build": "react-router build",

 "preview": "yarn build && wrangler dev",
 "build": "react-router build",

 "preview": "yarn build && wrangler dev",
 "build": "react-router build",

 "preview": "yarn build && wrangler dev",
 "build": "react-router build",

What am I doing wrong here? I want to test if my React Router 7 build works locally.

V

Vlady•3/29/25, 1:14 AM

I'm following the official template and the error is the same if I match the config and commands 1 to 1 https://github.com/cloudflare/templates/blob/staging/react-router-starter-template/wrangler.json

V

Vlady•3/29/25, 1:19 AM

I deleted this and it started working, not sure what generated it in the first place

T

thomasgauvin•3/30/25, 2:20 AM

How do you run a Worker project, within another Worker project? Wrangler seems to hang on detecting multiple wrangler.jsonc files, need to manually indicate which to use but it doesn't seem to be a parameter? https://developers.cloudflare.com/workers/wrangler/commands/#dev

Tthomasgauvin How do you run a Worker project, within another Worker project? Wrangler seems t...

M

MattIPv4•3/30/25, 3:49 AM

Try the

--config

--config

flag? It’s documented in other places as doing what you want here

T

thomasgauvin•3/30/25, 3:51 AM

Yep, that ended up working, thanks @MattIPv4

M

MattIPv4•3/30/25, 3:51 AM

And file an issue for updating the err to include that

T

thomasgauvin•3/30/25, 3:52 AM

Yeah, need to explain what's wrong + how to fix it in the error log, otherwise it's spam in the channel (like me rn)

M

MattIPv4•3/30/25, 3:52 AM

And if you want, an issue for the docs to make it clearer that’s a global flag :nod:

A

Alejandro Mery•3/31/25, 7:11 PM

hi, when trying to deploy from a dev container, I get a link for oauth but when approving it I'm told "No redirect uri set!" and later wrangler fails with "timed out waiting for authorization code"

any idea how to get this to work again?

A

Alejandro Mery•3/31/25, 7:13 PM

pnpm wrangler whoami

pnpm wrangler whoami

pnpm wrangler whoami

pnpm wrangler whoami has the same problem

no redirect uri set

A

Alejandro Mery•3/31/25, 7:34 PM

it used to work by opening a tunnel for

TCP6:[::1]:8976

TCP6:[::1]:8976

TCP6:[::1]:8976

TCP6:[::1]:8976 but now without a redirect url the whole thing breaks down

M

mau•4/2/25, 5:37 PM

Hey folks, I'm running into an issue with the WARP client.

Whenever I have WARP running, my fetch calls (in wrangler) break due to certificate errors. I’ve installed the Cloudflare certificate that WARP uses and tried setting the NODE_EXTRA_CA_CERTS environment variable to point to the .pem file (as suggested in the Workers SDK), but it's not working.

Is there something else I need to do to make wrangler trust the WARP cert? Or does WARP interfere in a way that can't be resolved just by trusting the CA?

Appreciate any help—thanks!

T

Tpf•4/3/25, 7:51 AM

Hi,

During dev cycles the worker I'm responsible for needs to have access to live (remote) KV data so I've always run

wrangler dev --remote

wrangler dev --remote

. This works fine.

Now I've added a durable object to the project and found that when running

wrangler dev --remote

wrangler dev --remote

the DO is evicted (including persistent storage) every few seconds and on every save of a file. This is a known issue (https://github.com/cloudflare/workers-sdk/issues/2700) that Cloudflare closed as 'not planned'. I see that using

wrangler dev --local

wrangler dev --local

wrangler dev --local

wrangler dev --local works alright for DO.

How does one develop a worker using both DO and remote KV? What am I missing? Is this just not something people are doing? Any advice much appreciated!

GitHub

🐛 BUG: wrangler dev Durable object storage resets after 10 secon...

Which Cloudflare product(s) does this pertain to? Workers/Other What version of Wrangler are you using? 2.9.1 What operating system are you using? Windows Describe the Bug If you use wrangler dev t...

M

Marcel Overdijk•4/4/25, 6:42 AM

Hi, I'm trying to migrating from @cloudflare/workers-types to wrangler types but it does not seem to work....
I've started with an empty template from

npm create cloudflare@latest -- --type openapi

npm create cloudflare@latest -- --type openapi

npm create cloudflare@latest -- --type openapi

npm create cloudflare@latest -- --type openapi
and then followed the migration steps here: https://developers.cloudflare.com/workers/languages/typescript/
so mainly:

npm uninstall @cloudflare/workers-types
npx wrangler types
Make sure your tsconfig.json includes the generated types
{
"compilerOptions": {
"types": ["worker-configuration.d.ts"]
}
}

M

Marcel Overdijk•4/4/25, 6:44 AM

but the tsconfig file already complains about:
Cannot find type definition file for 'worker-configuration.d.ts'.
The file is in the program because:
Entry point of type library 'worker-configuration.d.ts' specified in compilerOptions

and that file is genereated in my root folder as per the instructions.
and the

Env

Env

Env

Env interface is not recognized in other parts of the code...

MMarcel Overdijk but the tsconfig file already complains about: Cannot find type definition file ...

J

James•4/4/25, 12:28 PM

Is your repo public so we can take a look? Or can you share the generated file?

M

matthewlsessions•4/5/25, 4:36 PM

Just an FYI, the React on Workers with Assets template no longer serves with assets: https://github.com/cloudflare/workers-sdk/blob/d4c11710fd36286be8587379d659e19e91778777/packages/create-cloudflare/templates/react/workers/ts/worker/index.ts#L10

It conflicts with what is found in the docs: https://developers.cloudflare.com/workers/frameworks/framework-guides/react/

J

James•4/5/25, 5:15 PM

That looks to be expected - the Worker will only be run after Assets, and if one isn't hit. Do you have a reproducible example issue?

JJames That looks to be expected - the Worker will only be run _after_ Assets, and if o...

M

matthewlsessions•4/5/25, 6:56 PM

Right out of the box if you create the app through the CLI for workers with assets, then deploy the Worker handler is never invoked. See this screenshot as it should be return the Hello World json response:

M

matthewlsessions•4/5/25, 6:58 PM

During the deploy, it refers to a new wrangler config, that has a different entrypoint which ignores the worker fetch handler:

Using redirected Wrangler configuration.
 - Configuration being used: "dist/my_react_app/wrangler.json"
 - Original user's configuration: "wrangler.jsonc"
 - Deploy configuration file: ".wrangler/deploy/config.json"

Using redirected Wrangler configuration.
 - Configuration being used: "dist/my_react_app/wrangler.json"
 - Original user's configuration: "wrangler.jsonc"
 - Deploy configuration file: ".wrangler/deploy/config.json"

Using redirected Wrangler configuration.
 - Configuration being used: "dist/my_react_app/wrangler.json"
 - Original user's configuration: "wrangler.jsonc"
 - Deploy configuration file: ".wrangler/deploy/config.json"

Using redirected Wrangler configuration.
 - Configuration being used: "dist/my_react_app/wrangler.json"
 - Original user's configuration: "wrangler.jsonc"
 - Deploy configuration file: ".wrangler/deploy/config.json"

M

matthewlsessions•4/5/25, 7:11 PM

My current patch to make this work:

specify --config wrangler.jsonc in the build script
Add assets binding and directory to the assets in the wrangler config
Downgrade wranger-type to 4.0.0. (The newest version is not working. Giving type errors which is a separate problem)
Serve the assets in the handler (Like before this pr: https://github.com/cloudflare/workers-sdk/commit/efda570d7d98dce8bdbc6e8eff0ff920b6bbe985

I am not sure exactly what

update for SPA mode

update for SPA mode

update for SPA mode

update for SPA mode was intended to do, but the worker code is not being invoked at all.

GitHub

🫧 update for SPA mode in c3 templates (#8769) · cloudflare/wor...

remove unnecessary bits for spa mode
changeset
pr feedback
remove unnecessary env

J

James•4/5/25, 7:17 PM

Hmm that's very weird. I'd definitely recommend you raise an issue on the repo reporting the issues so the team can take a look

J

jed•4/5/25, 8:37 PM

is there any way to configure wrangler to support Durable Object IDs across reloads? ie, if i'm using

.newUniqueId

.newUniqueId

.newUniqueId

.newUniqueId to generate cookie values, then using

.idFromString

.idFromString

.idFromString

.idFromString to read them, this fails when my worker is reloaded. (this would be done specifying uniqueKey in workerd, i think: https://github.com/cloudflare/workerd/blob/main/src/workerd/server/workerd.capnp#L554)

GitHub

workerd/src/workerd/server/workerd.capnp at main · cloudflare/workerd

The JavaScript / Wasm runtime that powers Cloudflare Workers - cloudflare/workerd

Mmatthewlsessions My current patch to make this work: 1. specify --config wrangler.jsonc in the bu...

S

Silvan•4/5/25, 8:44 PM

oh interesting. i ran into something like this too. without using env.ASSETS i dont see how this is supposed to work (pretty sure it dosent)
because if you hit any subroute and refresh it will not respond anymore either

SSilvan oh interesting. i ran into something like this too. without using env.ASSETS i d...

M

matthewlsessions•4/5/25, 8:48 PM

Initially I thought they might be abstracting the assets handler away from us but that is not the case. Seems this PR should have never merged

Mmatthewlsessions Initially I thought they might be abstracting the assets handler away from us bu...

S

Silvan•4/5/25, 8:53 PM

well i thought the whole

"not_found_handling": "single-page-application"

"not_found_handling": "single-page-application"

"not_found_handling": "single-page-application"

"not_found_handling": "single-page-application"
is supposed to do exactly this. no more assets handler but it didnt work for me what so ever. unmatched routes are NOT redirected to the html without the asset handler

SSilvan well i thought the whole `"not_found_handling": "single-page-application"` is s...

M

matthewlsessions•4/5/25, 9:00 PM

I had a similar thought. Opened a bug for it: https://github.com/cloudflare/workers-sdk/issues/8798

GitHub

SPA mode in Wrangler SDK not every calling Worker Handler · Issue ...

Which Cloudflare product(s) does this pertain to? C3 (npm create cloudflare) What versions & operating system are you using? Wrangler 4.7 Node 20 Please provide a link to a minimal reproduction...

Mmatthewlsessions I had a similar thought. Opened a bug for it: https://github.com/cloudflare/work...

J

James•4/5/25, 9:09 PM

Oookay I just took a look at this, and it's due to the new

assets_navigation_prefers_asset_serving

assets_navigation_prefers_asset_serving

assets_navigation_prefers_asset_serving

assets_navigation_prefers_asset_serving compat flag that was enabled by default on April 1st. Now, if requests include the

Sec-Fetch-Mode: navigate

Sec-Fetch-Mode: navigate

Sec-Fetch-Mode: navigate

Sec-Fetch-Mode: navigate header, which happens on page navigation, and in SPA mode, the

index.html

index.html

or

404.html

404.html

404.html

404.html is served, instead of the Worker being invoked.

If you open your browser console and run

await (await fetch('/api/hello')).json()

await (await fetch('/api/hello')).json()

await (await fetch('/api/hello')).json()

await (await fetch('/api/hello')).json(), you'll see the expected response, and the Worker get invoked.

J

James•4/5/25, 9:10 PM

This is... very confusing behaviour imo. cc @GregBrimble @Sunil Pai

J

James•4/5/25, 9:13 PM

As a workaround if you wanted this to behave as you expect, add

assets_navigation_has_no_effect

assets_navigation_has_no_effect

assets_navigation_has_no_effect

assets_navigation_has_no_effect to your

compatibility_flags

compatibility_flags

compatibility_flags

compatibility_flags

S

Silvan•4/5/25, 9:14 PM

funny enough i had this issue before that flag was introduced.
unless im doing something wrong but from my understanding 404 should just be redirected, which dosent seem to be the case?

J

James•4/5/25, 9:16 PM

That looks like it is invoking your worker, but you're expecting it not to?

JJames That looks like it _is_ invoking your worker, but you're expecting it not to?

S

Silvan•4/5/25, 9:18 PM

correct
https://developers.cloudflare.com/workers/static-assets/#routing-behavior

You can configure and override this default routing behaviour. For example, if you have a Single Page Application and want to serve index.html for all unmatched routes, you can set not_found_handling = "single-page-application":

You can configure and override this default routing behaviour. For example, if you have a Single Page Application and want to serve index.html for all unmatched routes, you can set not_found_handling = "single-page-application":

You can configure and override this default routing behaviour. For example, if you have a Single Page Application and want to serve index.html for all unmatched routes, you can set not_found_handling = "single-page-application":

You can configure and override this default routing behaviour. For example, if you have a Single Page Application and want to serve index.html for all unmatched routes, you can set not_found_handling = "single-page-application":

if i remove the catchAll/notFound from my worker i get no response at all

SSilvan correct https://developers.cloudflare.com/workers/static-assets/#routing-behavio...

J

James•4/5/25, 9:19 PM

Do you have a project I can clone to reproduce? I'm not able to with the starter one from C3 + React: https://i.james.pub/file/2025/04/1c0c5551-57fe-4d34-b070-156843babb6e.png

S

Silvan•4/5/25, 9:20 PM

unless this might be an issue with hono and using something like

app.use('*',...)

app.use('*',...)

app.use('*',...)

app.use('*',...)

S

Silvan•4/5/25, 9:20 PM

i will to make a repro!

J

James•4/5/25, 9:20 PM

thanks, happy to take a look

JJames This is... very confusing behaviour imo. cc @GregBrimble @Sunil Pai

J

James•4/5/25, 9:24 PM

Yeah this is really unintuitive. I completely understand technically why it works the way it does - it's very "smart". But this isn't intuitive to how most people treat the web and their applications - people don't expect different behaviour with a

fetch

fetch

to a URL vs hitting it in their browser.

JJames Do you have a project I can clone to reproduce? I'm not able to with the starter...

S

Silvan•4/5/25, 9:26 PM

to be 100% sure here. my worker is supposed to programtically return a 404 right?
like in the template as in

return new Response(null, { status: 404 });

return new Response(null, { status: 404 });

return new Response(null, { status: 404 });

return new Response(null, { status: 404 });

J

James•4/5/25, 9:27 PM

in most cases the worker is only hit if there's no asset match

J

James•4/5/25, 9:27 PM

SPA mode adds a few more conditions

J

James•4/5/25, 9:27 PM

https://developers.cloudflare.com/workers/static-assets/routing/

JJames in most cases the worker is only hit if there's no asset match

S

Silvan•4/5/25, 9:30 PM

yea this is where the wording gets confusing
example.com > obviously index.html (routing works fine)
example.com/some/sub/page > no asset match and no worker route match? so it should also go back to index.html

talking about pressing refresh or directly navigating to the page with a URL

J

James•4/5/25, 9:31 PM

the worker "route" will never be checked and then go back to assets, unless you're doing that in your own code. It'll check for exact match, handle spa behaviour if needed, and then fallback to your user worker as the final step

J

James•4/5/25, 9:31 PM

I honestly couldn't tell you exactly what the logic is for how that works with SPA mode

J

James•4/5/25, 9:33 PM

we're talking about 2 different questions/issues here though for sure. Your's is slightly different to what @matthewlsessions is observing, which is the weird

assets_navigation_prefers_asset_serving

assets_navigation_prefers_asset_serving

assets_navigation_prefers_asset_serving

assets_navigation_prefers_asset_serving behaviour

JJames Oookay I just took a look at this, and it's due to the new `assets_navigation_pr...

G

GregBrimble•4/5/25, 9:34 PM

That’s correct, yes. I’m working on some more comprehensive docs at the moment (sorry for the delay in getting docs published before this change went live), but you can expect them to be live early next week. In the meantime, as @James says, you can add the

assets_navigation_has_no_effect

assets_navigation_has_no_effect

assets_navigation_has_no_effect

assets_navigation_has_no_effect flag if you wish to opt out. For most people though, we expect this change to be a welcome one. In traditional SPA setups, this will reduce the number of billable requests that you see in your application, without affecting functionality.

but this is definitely a really awkward aspect of developing with workers

Similar Threads