SS
JJ
fetchreturn new Response(null, { status: 404 });JJJSJJJassets_navigation_prefers_asset_serving behaviour
Gassets_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.GGJfetchwrangler/api/foo vs when they fetchwrangler dev
GET /api/foo - Received Sec-Fetch-Mode: navigate, serving <> or words to that effect, it'd help a lot with the confusion.
IGassets.not_found_handling is something other than “none”, that fallback is served (index.html for SPA, 404.html for 404-page).env.ASSETS.fetch(request) will likely no longer be necessary in most applications. They can now just return 404s or whatever.env.ASSETS.fetch(request), a response according to assets.not_found_handling is returned.GGG
JJ
BSJ404.html traverses up to find one, but index.html
Z
I
K
VV
wrangler dev
PPKKJJ
app.use('*',...)return new Response(null, { status: 404 });assets_navigation_prefers_asset_servingassets_navigation_has_no_effect/api/fooGET /api/foo - Received Sec-Fetch-Mode: navigate, serving <>assets.not_found_handlingassets.not_found_handlingenv.ASSETS.fetch(request)env.ASSETS.fetch(request)404.html