Recently I've been working hard to bring the custom renderer API to svelte!

This will unlock the ability to render a svelte component to something other than DOM: be It a native app, a PDF or even a terminal application. Let's explore the challenges we faced while working on it, how we surpassed them and what the future looks like.

Svelte 5 introduced runes which uses Signals under the hood. While Signals are very cool and unlock a ton of composability possibilities they have their own gotchas... let's explore them while creating a reactive signal based system from scratch to really understand them from the base!

Async tasks are a PITA to work on...they are messy, all over the place and the kinda smell bad. Just like sheep. But they can be tamed by an experienced shepherd/developer especially if they are accompanied by their trusty sheepdog.

The brand new view transition API is hot right now, sveltekit recently added a way to interact with it and while really powerful it's pretty low level. But what if there was a better way?

The brand new view transition API is hot right now, sveltekit recently added a way to interact with it and while really powerful it's pretty low level. But what if there was a better way?