That looks to be expected - the Worker will only be run _after_ Assets, and if one isn't hit. Do you
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?
MRight 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:
MDuring the deploy, it refers to a new wrangler config, that has a different entrypoint which ignores the worker fetch handler:
MMy 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
update for SPA modeGitHub
- remove unnecessary bits for spa mode
- changeset
- pr feedback
- remove unnecessary env
JHmm 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
Jis there any way to configure wrangler to support Durable Object IDs across reloads? ie, if i'm using
.newUniqueId.idFromStringGitHub
The JavaScript / Wasm runtime that powers Cloudflare Workers - cloudflare/workerd
Soh 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
because if you hit any subroute and refresh it will not respond anymore either
MInitially 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
Swell i thought the whole
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
"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
MGitHub
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...
JOookay I just took a look at this, and it's due to the new
If you open your browser console and run
assets_navigation_prefers_asset_servingSec-Fetch-Mode: navigateindex.html404.htmlIf you open your browser console and run
await (await fetch('/api/hello')).json()This is... very confusing behaviour imo. cc @GregBrimble @Sunil Pai
JAs a workaround if you wanted this to behave as you expect, add
assets_navigation_has_no_effect to your compatibility_flagsSfunny 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?
unless im doing something wrong but from my understanding 404 should just be redirected, which dosent seem to be the case?
JThat looks like it is invoking your worker, but you're expecting it not to?
Scorrect
https://developers.cloudflare.com/workers/static-assets/#routing-behavior
if i remove the catchAll/notFound from my worker i get no response at all
https://developers.cloudflare.com/workers/static-assets/#routing-behavior
if i remove the catchAll/notFound from my worker i get no response at all
JDo 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
Sunless this might be an issue with hono and using something like
Si will to make a repro!
Jthanks, happy to take a look
JYeah 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
fetchto be 100% sure here. my worker is supposed to programtically return a 404 right?
like in the template as in
like in the template as in
return new Response(null, { status: 404 });Jin most cases the worker is only hit if there's no asset match
JSPA mode adds a few more conditions
JSyea 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
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
Jthe 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
JI honestly couldn't tell you exactly what the logic is for how that works with SPA mode
Jwe'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
GThat’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 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.GThanks, as ever, for fielding questions, @James !
GDefinitely don’t dispute that it’s potentially confusing though! Hopefully updated docs help to clarify.
JYeah I think once people understand how it works, it might be welcomed, but for folks new to the platform or the web in general, it's very unintuitive. Expecting different responses when hitting a route in your browser vs
fetchwranglerI don't think anyone really expects to see a different response in their browser when they hit
/api/foo vs when they fetchYup, totally understand. And I think your idea of more comprehensive logging is absolutely a good one. If you’ve got specific suggestions here, I’m all ears. Otherwise, I’ll take a stab at something myself next week and see what we can do to make the request flows more obvious in
wrangler dev
JI think if there was a log that very clearly stated
GET /api/foo - Received Sec-Fetch-Mode: navigate, serving <> or words to that effect, it'd help a lot with the confusion.
I^ and would be immediately visible if users post their logs in here and we need to help them troubleshoot.
GLogic is:
- Check if request “exactly matches” an asset. If yes, serve.
- If no, but request is a navigation request, and new compat flag is enabled and
assets.not_found_handlingis something other than “none”, that fallback is served (index.html for SPA, 404.html for 404-page). - If not navigation request or flag is disabled, worker script is invoked if present. Since this is now happening after the fallback serving in typical SPA modes, an assets binding and final
env.ASSETS.fetch(request)will likely no longer be necessary in most applications. They can now just return 404s or whatever. - Finally, if the worker script either isn’t present or does
env.ASSETS.fetch(request), a response according toassets.not_found_handlingis returned.
GI’m on mobile right now, so can’t try to repro, but if something isn’t following that, I’m pretty sure it’s a legit bug.
G“Exactly matches” is in quotes to hand wave over HTML handling.
GAgain, this’ll all be documented more formally next week. Apologies for this rough first draft 
JThanks. When you're next available, taking a look at the example @Silvan posted in https://canary.discord.com/channels/595317990191398933/1358194995076796507/1358195325306802306 might help a bit. I think what's happening is technically expected, but not what I would expect intuitively. I couldn't tell you why the SPA behaviour isn't working for them at all on a compat date prior to April 1st - I must be missing something.
JIn the future, it might be preferrable to not enable things like this so quickly by default when the documentation/education/logs around it aren't complete yet 
Bnot sure where to post this but please...
- can we please allow upload .env directly for build variables ? it is annoying we have to upload one by one thorugh the ui ( regular env var seems like support pasting dotenv) - when using sveltekit we have to provide them for build .. and i think in pages, all env variables are also used as build variables
- is there an max limit for build variable for workers ? once my build var reach 50+ i got Initializing build environment... internal error occurred. Please retry your build. If this problem persists, contact Cloudflare support.
Stechnically it makes 100% sense else i dont get how this would even work
but this needs to be documented very clearly in 1 place else its very hard to find the connection between all these things
but this needs to be documented very clearly in 1 place else its very hard to find the connection between all these things
JIf I'm reading correctly, it looks like the
404.htmlindex.htmlI've not tested and haven't looked that closely at this code, but that looks like what it's doing
Zi reran npx wrangler types to generate a new worker-configuration.d.ts, and instead of doing this:
interface Env {
...
}
it did:
declare namespace Cloudflare {
interface Env {
...
}
}
interface Env extends Cloudflare.Env {}
and now my env doesn't work anywhere... (context.cloudflare.env doesn't have any of my types on it) Has anyone run into this or know how to fix it? (this is in a remix app, but I've updated to wrangler 4 and been using it fine for a bit...)
interface Env {
...
}
it did:
declare namespace Cloudflare {
interface Env {
...
}
}
interface Env extends Cloudflare.Env {}
and now my env doesn't work anywhere... (context.cloudflare.env doesn't have any of my types on it) Has anyone run into this or know how to fix it? (this is in a remix app, but I've updated to wrangler 4 and been using it fine for a bit...)
II'm having the exact problem. Spent an hour reading docs, forums, but didn't find any solution. Came here (discord) in hopes of fix, but seems you didn't get any help either. Not a good first impression for this tool..
