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.

A reflection on how what I've learnt about Svelte in the last few weeks fits into the context of what I've learnt in the last 30 years of software development.

Although perhaps more suited to those new to Svelte or Svelte-curious, it will hopefully also still be of interest to a wider audience.

Discussing the process and challenges of creating Melt UI, alongside some unique benefits that Svelte brings to the table (SvelteKit packaging, preprocessors, actions, etc). Together with a demonstration of the current builders available.

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!