Skip to content

Document why edge deployment is disabled in Netlify adapter config #352

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
bartveneman wants to merge 1 commit into
base: main
Choose a base branch
from
+4 −0
Open

Document why edge deployment is disabled in Netlify adapter config #352

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions svelte.config.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
Loading