Paolo Ricciuti - Svelte

[hipstersmoothie]

devtools.fm Podcast Outline: Paolo Ricciuti

Guest: Paolo Ricciuti
Role: Svelte Maintainer & Ambassador, Senior Software Engineer at Mainmatter
Focus: Svelte ecosystem, developer tooling, MCP servers, custom renderers

---

Questions

Background & Origin Story

• What drew you into web development initially, and how did you end up becoming a Svelte maintainer?

---

Svelte 5 & The Runes Revolution

• Svelte 5 was a ground-up rewrite introducing Runes. What was it like being part of this massive undertaking, and what parts did you contribute to?

Svelte 5 introduced runes ($state, $derived, $effect) as a new reactivity paradigm powered by signals. This was a fundamental shift from Svelte 4's implicit reactivity. Paolo has been actively contributing to the core compiler and runtime.

• Svelte 5 release announcement
• Paolo's GitHub contributions to sveltejs/svelte

• You gave a talk called "Surprise! Svelte Secretly Sending Signals" at JSNation. Can you explain how signals work under the hood in Svelte 5 and why understanding this matters for developers?

This talk walks through implementing a basic reactivity system with signals to help developers understand the gotchas and patterns. It's a great window into how Paolo thinks about teaching complex concepts.

• JSNation talk
• Speaking page

• What's the story behind async Svelte? Being able to await directly in components seems like a game-changer.

Async Svelte allows using await anywhere in components without wrapping in boundaries. This eliminates entire categories of boilerplate around data fetching and loading states. The feature is now in experimental status.

• Async Svelte announcement
• Svelte Radio episode on Async Svelte

---

TMCP: Rethinking MCP Server Development

• You built TMCP as an alternative to the official MCP TypeScript SDK. What problems did you encounter with the official SDK that motivated this?

TMCP offers schema-agnostic validation (works with any library through adapters), minimal dependencies (no Express), and a unified API. Paolo has been vocal about design issues in the official SDK, even opening issues and contributing back.

• TMCP GitHub repo
• Mainmatter blog post on MCP
• Issue Paolo opened on official SDK

• Walk us through the design decisions behind TMCP—the adapter pattern for schema validation, transport separation, etc.

The architecture treats MCP as fundamentally a JSON-RPC server, separating concerns cleanly. This enables using different validation libraries (Valibot, Zod, etc.) and different transports (stdio, HTTP) without coupling.

• TMCP npm page
• The Context talk on TMCP

---

The Official Svelte MCP Server

• You helped build the official Svelte MCP server. How does the "autofixer" technique work, and why is it so effective for improving LLM-generated Svelte code?

The Svelte MCP server uses static analysis to detect common patterns, anti-patterns, and migration opportunities in generated code. The autofixer can be called in an agentic loop until issues are resolved, creating a feedback cycle that dramatically improves code quality.

• Svelte MCP docs
• MCP tools documentation
• Hacker News discussion

• Your talk "How I taught LLMs how to Svelte" at The Context covered this work. What surprised you most about making LLMs understand Svelte 5's new patterns?

Releasing Svelte 5 with a major syntax rewrite right before LLMs got good at code was challenging timing. The MCP server approach provides real-time context that training data can't match.

• Speaking page - The Context talk
• Using Svelte MCP tutorial

---

Custom Renderers for Svelte

• You're leading the initiative to bring custom renderers to Svelte. Can you explain why React can render to native/terminal/video but Svelte currently can't?

React separates its reconciliation logic (React) from rendering (React DOM, React Native, Ink, etc.). Svelte's compiler approach makes this harder—it's tightly coupled to the DOM through patterns like the <template> element trick. Paolo's work addresses this architectural challenge.

• Custom Renderers for Svelte website
• Mainmatter blog post
• GitHub issue

• You built a proof-of-concept for Svelte + Lynx (ByteDance's native framework). What was that experience like?

Lynx is backed by ByteDance and offers a framework-agnostic core. Paolo spent days of trial and error with minimal documentation, eventually getting Svelte to render natively on a phone screen through Lynx.

• Lynx GitHub issue requesting Svelte support
• Svelte Radio episode on custom renderers

• What use cases beyond native apps does the custom renderer API unlock?

Terminal UIs (like Ink for React), WebGL canvases (Threlte), PDF generation, video creation (like Remotion)—all become possible with a proper custom renderer API.

• Svelte Radio discussion

---

Future of Svelte

• What's on the roadmap for Svelte that you're most excited about?

Recent additions include async Svelte, remote functions, attachments (the evolution of actions), and the fork API. What's coming next?

• What's new in Svelte: November 2025
• Advent of Svelte 2025

• What do you think the future of frontend development looks like? Is the compiler-first approach becoming mainstream?

Svelte pioneered the idea that frameworks should compile away. With Svelte's growing adoption and the signals paradigm spreading, how does Paolo see the landscape evolving?

---

Guest Links

• Website: ricciuti.me
• GitHub: github.com/paoloricciuti
• Bluesky: @paolo.ricciuti.me
• SvelteLab: sveltelab.dev
• TMCP: github.com/paoloricciuti/tmcp
• sveltekit-search-params: github.com/paoloricciuti/sveltekit-search-params
• Speaking: ricciuti.me/speaking
• Mainmatter: mainmatter.com