It’s that time of the year again guys, get ready

Really thankful today for @rich-harris.dev, @dummdidumm.bsky.social, and all of the rest of the @svelte.dev team. Four years ago, when I discovered Svelte and SvelteKit, I never could have known that working on them full time would be paying the bills.

Ready for Advent of Svelte 2025? 👀 advent.sveltesociety.dev/2025

Tfw you fix a bug nobody noticed thanks to your detailed analytics

lazygit is so good

I'm looking for my next opportunity in the front-end space 🌐 I've worked at some great companies: Hugging Face, V7, Appwrite, and Significa. I've built NPM packages with 400k downloads/week, and am an avid open-source contributor. Let me know if you want to work together!

Streaming file uploads via a custom binary format just got merged into SvelteKit! In a follow up PR (github.com/sveltejs/kit...) upload progress will be handled too! github.com/sveltejs/kit...

Nothing to see here, just a few Svelte milestones. For SvelteKit alone I'd need to add 6+ more notable user-land features. I'm thinking about turning this into a less noisy interactive (with links).

This is now a fixed problem! You can now prefix issues/PRs/discussions with both Svelte Changelog domains from the _very beginning_ of the link! 🥳

pretty excited about this feature (thanks @ottomated.net!). dealing with file uploads can be a bit of a pain — the way it works normally is that you (or your framework) does `await request.formData()` to get a FormData object. but it has to buffer every file into memory first. that's a problem!

9 years ago from today @rich-harris.dev made the first commit to @svelte.dev 🍰 github.com/sveltejs/sve...

Starting learning Rust, wish me luck

🫡 because it’s best-in-class

TIL about svelte-changelog.dev Goodbye reading individual CHANGELOG files on Monday morning, hello single-source-of-truth 😅

I don’t get why bsky didn’t implement yet a way to quickly visit someone’s handle website It would only work for custom domains ofc but it’d be such a nice QOL

Svelte Changelog just reached 50 stars! It ain’t much but it’s my most starred repo and your support means a lot! 🥳⭐️

Big new thing on Svelte Changelog: you can now prefix a GitHub URL with the whole new shortened "svcl.dev" domain to open an issue, PR, or discussion in SC directly from GH! 🔥

New nice little improvement in Svelte Changelog: you can now navigate between referenced issues/PRs/discussions from hashes in the descriptions! 💨

another async feature: out-of-order rendering. this means a component can begin rendering children while it's awaiting data. demo stolen from @ryansolid.bsky.social — these components should render in 3 seconds, but they only take 1: svelte.dev/playground/2...

(It took Rich only 2 days to drop this, it just went out)

this is auto-enabled in SvelteKit 2.48 which we released a few minutes ago. just need to have the latest Svelte version and opt into the `experimental.async` feature (svelte.dev/docs/svelte/...)

part 5 is to enable parents and children to do work in parallel — right now, <Page> won't start loading anything until <Layout> is ready to render <Layout><Page /></Layout> ...but we're on it 😁 github.com/sveltejs/sve...

The Master Plan is approaching its completion, time to bring forking in SvelteKit and get everything out of experimental! 🔥 bsky.app/profile/antl...

this is what the combination of a signal graph and a compiler gets you. it's super efficient in terms of both CPU and memory (and developer effort) there's still a couple more pieces to the async puzzle that we need to sort out, but it's coming together better than i ever thought possible

Hello, friends! After 10(!) years of #AdventOfCode, I've made some changes to preserve my sanity: there will be 12 days of puzzles each December (still starting Dec 1) and there is no longer a global leaderboard. Read more: adventofcode.com/2025/about#f... adventofcode.com/2025/about#f...

Biome v2.3 is out! 👨‍👨‍👦‍👦 Full support for @vuejs.org, @svelte.dev and @astro.build ‼️ New ignore syntax 🌬️ Tailwind v4 support ⌨️ New CLI flags and reporters biomejs.dev/blog/biome-v...

Thanks for everything... it's just so nice to use for This Week in Svelte (and I feel bad for just clicking on the link to open the PR on GitHub sometimes 😅) 🤟🏻

New batch of updates for Svelte Changelog! Nothing huge, but a set of QOL improvements that will make the overall experience better. Let's dive right in! 👇

Beat the size of my block-only component (I think I really need to try async Svelte)

Answer: yes! The Svelte team cooked once again (Ignore the multiple log lines, I tried multiple times)

Does query.batch batch calls across components boundaries? I.e. if I call the same endpoint in +layout, +page & a subcomponent, are they all batched together?

I should spin up a small Playwright test suite for Svelte Changelog

I’d like to server-side benchmark/flamegraph a SvelteKit API endpoint, does anyone know how to do that? (Not only an API endpoint, but flamegraph-ing parts of server-side SvelteKit would be really neat to do)

Svelte Changelog now features dynamic OG images! All the pages now cleanly renders an appropriate image when shared on all platforms

Barely 8 hours since the sveltejs/mcp repo is public, no official post has yet been done, but @sveltejs/mcp is already live on Svelte Changelog! 🔥👀 @paolo.ricciuti.me and @khromov.se decided to make the repo public a few hours before my vacation flight, but that's a failed attempt at stopping me!!

I *love* this kind of tutorial/example video from the team itself! So useful to get started on this whole new paradigm in Svelte! 🔥

I‘m monitoring svelte-changelog.dev now. If you like you can set up one of the supported notification methods (Telegram bot, Signal, PushOver etc - full list: github.com/louislam/upt...) and I can make Kuma send the notifications to you directly!

My RSS feed is happy again. Thanks for fixing this!

Update: it was a one-line fix! The very recent use of changesets by @dummdidumm.bsky.social for the language-tools repository completely broke the logic of the website for releases in this repository, causing a fatal error at startup (serverless) 😅 The site was down for the day, sorry about that!

Svelte Changelog is currently completely down I honestly have no clue what’s happening There’s an issue tracking that problem More info when I get home tonight

I’d love to get a "What’s new in Svelte" page into Svelte Changelog It would essentially be a list of small articles demoing the new features as they ship The thing is making that automatically is lowkey impossible, and maintaining that for almost every minor is VERY time consuming Any ideas?

Update: I did it! svelte-changelog now leverages @shiki.style's/tm-grammar languages to detect a snippet's actual language automatically! 🔥 Syntax highlighting detection across the site is now MUCH more reliable!

I think I’m on a good track for making an auto-detect based on Shiki a reality 👀🤔

TFW you try releasing a new version of your package with OIDC after you learnt it from @benmccann.com in TWIS, but you fall into the UNDOCUMENTED EDGE CASE where you CANNOT use npmjs dot com despite it being the new default domain, it HAS to be npmjs dot org otherwise 404...

SvelteKit 3 will drop 17% of dependencies thanks to new APIs now available directly in Node. We could drop another 17% if Node were to add support for cookie parsing and serialization.

Alright, that was quite a productive work weekend on Svelte Changelog! Let's unwrap what's changed! 🧵

Edit: guys guys I got it!! It's not _perfect_ cause it breaks on HMR sometimes (not a big deal) and it requires hydration before reflecting the true state, but it won't be noticeable from the user's perspective Thanks @paolo.ricciuti.me and @fubits.dev for your tips!

In order to bring (back) features into Svelte Changelog, I need my +page to react to a control (checkbox) state change that is in my +layout The control state also needs to update on page change, because each page can have a diff. state What’s the best way to achieve that? Context? Shared rune(s)?