If you're migrating from Svelte 3 to 5, I recommend starting with the Svelte 3 to 4 migration guide: svelte.dev/docs/svelte/... and then continue with the Svelte 5 migration guide you found.
There's also a script that helps automate this: `npx svelte-migrate@latest svelte-4`.
Hi! As you may note in that document, `$: ` labelled syntax is replaced with either the `$derived` (preferred) or `$effect` (allowed, but discouraged) Runes.
Sorry for the late reply. Are you using Vite 8? That may have some bugs; otherwise if you can please share a repo or Stackblitz reproduction me or others can dig into it.
Are you asking about Astro apps consuming Svelte components?
In static, prerendered, or server rendered cases, component CSS should be available via `<link>`. And when doing client side navigation, those same `<link>` elements are injected via JS.
Are you still using Toasts in your UI? Consider other forms of feedback instead.
Related reading: primer.style/accessibilit...
Oh yeah, now I get it. That's a fun sport. I've wanted to do something like that for a while; maybe as a head-to-head pre-recorded session turned to supercut. Though a TWIS long cut would be a great start.
It was covered before, but definitely worth bringing up again: www.youtube.com/live/1a-iKUC...
I remember you shared this related video with me as well: youtu.be/aKxcIQMWSNU?...
I'm learning something new from Paolo constantly. Follow them!
For me it's `tick`; when it comes to focus management it's very straightforward to change a reactive value that impacts DOM visibility and then focus on the then-visible element.
list = await someData() // stateful
await tick()
listContainer.focus()
This talk was presented at FITC Web Unleashed on October 20, 2025.
If you reply here I'd be happy to discuss or critique points made from the talk!
In my talk, "Build Robust Components" I share stories, techniques, and real world considerations that motivate a usable experience before and after JS hydration.
youtu.be/Sf0DlcPPNTE?...
here's a brief look ahead at what we have planned in the e18e community for 2026 🎉
great collaborations, and many useful developer tools are in the works.
also a huge thanks to all who contributed so far - many of the libraries, tools, and frameworks we use today are faster because of you 💙
I don't know the Rust ecosystem very well, but I'm guessing Boa can maybe get the job done: github.com/boa-dev/boa
Or perhaps Rolldown can integrate (or maintain) an engine.
To be clear, Goja is a JavaScript engine written in Go, not a Node.js wrapper. I'm suggesting an interpretation layer would be more pluggable than to have many ports of JS libraries or frameworks; kinda like how Rosetta translates architectures at runtime.
I think a more scalable outcome would be a compatibility layer between JS and Rust; and maybe one already exists. For example, there's "goja" for interpreting JS in a Go runtime, which allows this framework to render Svelte on the server using Go without required Node.js: github.com/nichady/golte
Okay, done. Changes should reflect within 24 hours.
We've released fixes for 5 CVEs affecting the Svelte ecosystem. Please upgrade your apps!
Read the post to learn if you're affected:
svelte.dev/blog/cves-af...
Svelte.dev landing page, with annotation circling the pronunciation of "Svelte" as /ˈsvɛlt/ per IPA guide.
You can send them to the front page: svelte.dev
*30-minute
I guess typos live forever here.
It's also worthwhile to practice some leetcode and 30-minite React exercises. It certainly helped me in my job search a few months back.
Once you land an interview, you can show them your deeper web development knowledge beyond frameworks.
Unfortunately, hiring for React is a thing. Some recruiters may filter out candidates who don't mention React on their resume, or don't have React projects on GitHub.
Porting your projects to React sounds like a good idea to me.
Choosing "HTML" as your syntax language seems to work well.
I haven't explored this deeply, but I think this VSCode extension could work: marketplace.visualstudio.com/items?itemNa...
But it needs Svelte support: github.com/zignd/HTML-C...
I'm guessing you want a very small SBOM, and be able to return to the codebase a year later without needing to migrate a lot.
Svelte + Vite is a reasonably safe bet, but nothing can beat pure HTML/CSS/JS if longevity is a major factor.
Anything with OpenAPI integration. It could be Fastify + oRPC, Hono, or maybe Elysia.
AI coding sucks
CJ just one-shotted a 15 min rant and it's incredibly refreshing.
www.youtube.com/watch?v=0ZUk...
This is such a great idea. I just chose and ranked my favorite 15 features in the list—primarily CSS and HTML features of course. interop-rank.jakearchibald.com
What are yours?
I definitely agree with leaning into evergreen or standard concepts. One thing that helps me is to write most logic and state server side so that my JS is evergreen, and the front end is mostly plain HTML and CSS without complex reactivity or local handlers.
