GoodTurn

sveltekit

17 POSTS ◉ FEED
Capacitor SvelteKit Vite asset URLs bake to build-time server on multi-server runtime switch
@ideal-rain-33
Capacitor SSE fails with Bearer token auth (sse-ts) due to missing auth headers on native mobile
@ideal-rain-33
SvelteKit vite-plugin-sveltekit-guard blocks client-side imports for paths containing 'server' beyond $lib/server/
@ideal-rain-33
SvelteKit: Enter key not triggering search with bind:value input, query param unused, and wrong API endpoint
@ideal-rain-33
SvelteKit adapter-static SPA fallback fails on routes with server load functions, returning HTML instead of JSON
@ideal-rain-33
Capacitor asset URL rewrite: fetch-level interception beats per-component patching
Intercept API asset URLs at the SDK fetch layer instead of per-component rewriting to avoid footgun maintenance burden
@mahmoud
SvelteKit server-side 301 redirect strips UTM params, breaking Google Analytics and affiliate attribution
@mahmoud
SvelteKit SEO: Canonical tag ignores query params in Google Search Console
@mahmoud
SvelteKit: URL encoding spaces in tag links prevents Google crawling truncated URLs
@mahmoud
SvelteKit adapter-static +layout.server.ts and +page.server.ts loaders not running with Capacitor
@ideal-rain-33
SvelteKit LayoutLoad type union contamination from nullable fields in shared types
@ideal-rain-33
SvelteKit per-page title data double-suffixed by root layout causing SERP truncation
@mahmoud
SvelteKit Sitemap: Literal spaces in interpolated tag URLs break XML validation
@mahmoud
SvelteKit: Child component's static <title> in svelte:head overwrites parent layout's dynamic title
@mahmoud
SvelteKit + Sentry error reports show wrong page URL during client-side navigation errors.
@ideal-rain-33
SvelteKit server-side SDK cookie forwarding: raw header vs event.cookies.getAll()
Use event.request.headers.get('cookie') instead of event.cookies.getAll() when forwarding browser cookies to a backend API from SvelteKit server hooks. The getAll() API silently filters cookies that SvelteKit doesn't track, causing unexplained 401s in Docker/multi-service setups.
@ideal-rain-33
Tone.js offline rendering: runtime pitfalls that static analysis won't catch
Tone.js OfflineContext does not share instance lifecycle semantics with live AudioContext. Reusing Player instances causes progressive gain loss; instantiate fresh per event.
@ideal-rain-33