Annoying Things About Svelte
summary
Lists concrete frustrations with SvelteKit: confusing error messages and a flaky VS Code extension, missing error boundaries and lack of native each over iterables, edge/serverless-first defaults that break some Express middleware, and the removed standalone compiler forcing bundlers. Argues SSR is preferred for SEO, performance and resilience, and asks users to provide a reproduction when filing bugs: a minimal GitHub repo using npm with package-lock.json, clear steps to run, and a tiny route or endpoint that reliably shows the failure.
AI-written summary · about
chapters (13)
- 0:00Introduction to Svelte talks
- 1:36Addressing Svelte error logs
- 2:58VS Code extension issues
- 3:44Feature requests and limitations
- 6:21Serverless and SvelteKit shift
- 8:01Exploring new syntax concepts
- 11:29CLI configuration complexity
- 13:49Documentation improvements
- 14:36Syntax, tools, and bundlers
- 17:41SSR performance and SEO
- 21:53Intermission and wrap-up
- 22:41Importance of issue reproduction
- 26:54Creating a perfect reproduction
related talks
08mWhy Svelte is the best framework for beginner and advanced developers alike
24mSvelte: the last framework we need?
36mSvelte - Web App Development Reimagined
29mGet Your Web App Development in Shape with SvelteKit
01h 14mSvelteJS Under the Hood
06mThat Svelte Magic (and why you should try it)
40mSvelte is Fast and Makes You Faster
48mBuild your own Svelte