From 57272e9a6962ee4b27f781c47381d209384643a7 Mon Sep 17 00:00:00 2001 From: Claude Date: Thu, 16 Jul 2026 17:40:01 +0000 Subject: [PATCH] Document why HTTP 103 Early Hints isn't implemented SvelteKit has no API for sending an actual early-hints response, and Netlify Functions (which this adapter targets) can't send an informational response ahead of the final one anyway. Note this next to the edge:false decision it's tied to. Co-Authored-By: Claude Sonnet 5 Claude-Session: https://claude.ai/code/session_01NE7tjjv8RUN1wPHYmFmaFf --- svelte.config.js | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/svelte.config.js b/svelte.config.js index d6e64fd5..41fe71bd 100644 --- a/svelte.config.js +++ b/svelte.config.js @@ -16,6 +16,10 @@ const config = { adapter: adapter({ // We don't generate enough traffic to keep edge workers ready, so disable edge to avoid cold-starts // Also cannot run on edge because stylelint requires NodeJS-specific APIs + // Side effect: also rules out HTTP 103 Early Hints, since that needs a layer that can send + // an informational response before the final one, which Netlify Functions can't do (edge might, + // but Netlify has no documented support for it either way, unlike e.g. Cloudflare). SvelteKit + // itself has no early-hints API, only an auto Link:rel=preload header on the final response. edge: false, // We split the bundles to not impact other routes with Stylelint's slow start split: true