https://github.com/Sillyvan/asset_
8 Replies
Will take a look at this in a sec
oh okay nvm. i just did
"compatibility_date": "2025-04-01",
now the SPA mode works. aka directly doing /todo works BUT same issue now as above
doing /test (which is a direct worker match) dosent work anymore nowWhat if you
fetch('/test') in your console?yep that one indeed invokes the worker as expected. still insanely weird behaviour imo.
agreed
Hey, thanks for posting the example repo. Here's what I'd expect a pre-2025-04-01 project to look like: https://github.com/Sillyvan/asset_handling_spa/pull/1. You were just missing the fallback that's necessary without this new compatibility flag.
And here's what I'd expect a post-2025-04-01 project to look like: https://github.com/GregBrimble/asset_handling_spa/pull/1
I think that's everything working as we, as Cloudflare, expect. Let me know if you have any questions!
GitHub
Build software better, together
GitHub is where people build software. More than 150 million people use GitHub to discover, fork, and contribute to over 420 million projects.
GitHub
Post 2025-04-01 SPA fix by GregBrimble · Pull Request #1 · GregBr...
When using the assets_navigation_prefers_asset_serving compatibility flag, navigation requests are served by assets automatically, so you do not need to manually fallback from your Worker script. T...
I think many were expecting the SPA flag to behave like assets_navigation_prefers_asset_serving by default! (which it does now)
but to me its clear now but thanks for going into detail
Yeah I think this is a net win once people understand what's happening. Hopefully we can get some clear logs about that so it's immediately obvious and doesn't take a bunch of folks hours in the discord to debug back and forth, haha https://github.com/cloudflare/workers-sdk/issues/8798#issuecomment-2783413060