Latest updates and changelog for Svelte and SvelteKit. Deep dive and demonstration of s-kit, a SvelteKit toolkit for composing responsive email templates and simplifying template creation.
Updates and features in the Svelte ecosystem. The episode starts with a discussion on Svelte 5.7.4, highlighting bug fixes related to inert effects, component destruction, and store access. It also introduces new features like allowing the 'const' tag inside Svelte boundaries and ensuring consistent signal writing validation. The episode then delves into SvelteKit updates, including improvements in handling redirects, preloading, and dynamic dependencies. Additionally, it mentions the removal of post-install scripts due to security concerns and the introduction of new types for page and layout props. The episode concludes with a community showcase featuring Svelte Radar, a VS Code extension that provides a visual overview of SvelteKit routes, making navigation and development more efficient.
Changelog and a showcase of Threlte 8, which fully supports Svelte 5. The episode discusses various updates and fixes in Svelte, including improvements in file binding, reactivity, and template effects. The main highlight is the presentation by Gisha, the creator of Threlte, who demonstrates Threlte 8's capabilities, including its integration with Svelte 5 and the introduction of Threlte Studio, a tool for 3D development with Svelte.
Svelte updates and a showcase by Eno on a new component called Svelte Cartesian. The episode starts with a changelog covering various fixes and improvements in Svelte, including event handler changes, input value handling, and CSS pruning. Eno then presents Svelte Cartesian, a tool for visual regression testing that helps render all combinations of a component's props for testing purposes.
Changelog and Q&A with Rich Harris. The episode covers various updates and improvements in Svelte, including support for TypeScript type assertions, fixes for scoping classes, optimizations in the compiler, and enhancements in SSR (Server-Side Rendering) and CSS pruning.
Skeleton v3.0, a significant update to the Skeleton library. The episode covers various changes and improvements, including better TypeScript support, handling of hydration mismatches, and new features like state fields in class constructors. The host discusses the importance of Skeleton in the Svelte ecosystem and its role in providing a design system with themes and components.
Updates and showcases in the Svelte ecosystem. The episode begins with a changelog for Svelte 5.33.15, highlighting fixes and improvements such as boundary error handling for derived stores, regression fixes in destructuring props, and updates to the AON parser. The showcase features Svelte Lexical, a rich text editor for Svelte based on Lexical from Facebook.
Svelte Flow, a library for building interactive flow UIs with Svelte. The episode starts with a changelog discussing recent updates and fixes in Svelte, including improvements to the inspect function, fine-grained template usage, and support for state mutations in derived objects. The main segment features Peter from XY Flow, who demonstrates how to use Svelte Flow to create and customize nodes, edges, and handles in a flow UI.
Updates in the Svelte ecosystem, including changes in Belt, a library for Svelte. The episode discusses bug fixes, new features like getAbortSignal, and improvements in the reactivity system. It also highlights the release of Ark UI, a component library for Svelte, and its integration with the Svelte ecosystem.
Latest updates and features in the Svelte ecosystem, particularly around SvelteKit. The episode highlights the introduction of experimental async SSR (Server-Side Rendering), which allows for asynchronous operations directly within Svelte components, significantly improving developer experience.
I've tried Svelte Native recently for building an iOS/Android app for a web-based app that already built with Svelte, and it was quite successful! In this session, I'm going to show how Svelte Native works (also with NativeScript a little bit), how much you can reuse code from the Svelte-based web counterpart or what exactly you cannot, and how it suites for full-stack engineers thanks to dramatically reduced costs of context switches between web and mobile (since both are in Svelte!).