Kilian Schulte
@schultek.dev
I maintain open source packages for Flutter and Dart, mainly Jaspr and dart_mappable. 💙🎯
Always looking for chaos 🤣
October 15, 2025 at 1:45 PM
Always looking for chaos 🤣
🪄 With the latest Jaspr VSCode extension, you can now Copy-Paste raw HTML into your editor, and have it magically converted into valid Jaspr code.
September 23, 2025 at 6:53 AM
🎯 Introducing Component Scopes for Jaspr!
With the newest release, you get live in-editor hints on where a component is rendered (server, client or both) and whether it uses unsafe imports.
This is solving one of the biggest pains when working with full-stack components 👇
With the newest release, you get live in-editor hints on where a component is rendered (server, client or both) and whether it uses unsafe imports.
This is solving one of the biggest pains when working with full-stack components 👇
September 21, 2025 at 7:01 AM
Super hard problem to solve. If you have any idea how let me know.
September 20, 2025 at 8:41 PM
Super hard problem to solve. If you have any idea how let me know.
Component scopes are enabled by default for all Jaspr projects when using the latest VSCode Extension.
Check the release notes for more details: docs.jaspr.site/releases/pac...
Check the release notes for more details: docs.jaspr.site/releases/pac...
VSCode Extension Version 0.2.2
Release notes and changes.
docs.jaspr.site
September 20, 2025 at 7:59 PM
Component scopes are enabled by default for all Jaspr projects when using the latest VSCode Extension.
Check the release notes for more details: docs.jaspr.site/releases/pac...
Check the release notes for more details: docs.jaspr.site/releases/pac...
When using server-side rendering or static site generation, components may be rendered in different environments (server vs client).
Keeping track for each component is complex and tedious and can lead to unexpected behavior or even compilation errors due to wrong imports. 👇
Keeping track for each component is complex and tedious and can lead to unexpected behavior or even compilation errors due to wrong imports. 👇
September 20, 2025 at 7:59 PM
When using server-side rendering or static site generation, components may be rendered in different environments (server vs client).
Keeping track for each component is complex and tedious and can lead to unexpected behavior or even compilation errors due to wrong imports. 👇
Keeping track for each component is complex and tedious and can lead to unexpected behavior or even compilation errors due to wrong imports. 👇
Jaspr + Riverpod = 💙
jaspr_riverpod is not updated to use Riverpod 3, giving you access to all the latest features.
Also, syncing providers is now even easier. Think "fullstack providers" that you compute on the server (e.g. load from db) and read on the client after pageload.
jaspr_riverpod is not updated to use Riverpod 3, giving you access to all the latest features.
Also, syncing providers is now even easier. Think "fullstack providers" that you compute on the server (e.g. load from db) and read on the client after pageload.
September 18, 2025 at 3:51 PM
Check the docs for more info: docs.jaspr.site/eco/riverpod...
Jaspr Riverpod
A port of the riverpod package for Jaspr.
docs.jaspr.site
September 18, 2025 at 3:50 PM
Check the docs for more info: docs.jaspr.site/eco/riverpod...
Jaspr 0.21.0 is out! 🐾
It comes with:
✒️ Simpler and more Flutter-like syntax
🪄 Optimized performance and stability
🎨 More styling properties
Oh, and all breaking changes can be migrated fully automatically.
Check 🧵for details
It comes with:
✒️ Simpler and more Flutter-like syntax
🪄 Optimized performance and stability
🎨 More styling properties
Oh, and all breaking changes can be migrated fully automatically.
Check 🧵for details
September 17, 2025 at 10:12 AM
migrate 99% of your components automatically.
Internally, this change allowed for deep optimizations in the framework, resulting in better performance, stability and less complexity (easier to maintain + contribute).
Read the full release notes here:
docs.jaspr.site/releases/v/0...
Internally, this change allowed for deep optimizations in the framework, resulting in better performance, stability and less complexity (easier to maintain + contribute).
Read the full release notes here:
docs.jaspr.site/releases/v/0...
Version 0.21.0
Release notes and breaking changes.
docs.jaspr.site
September 13, 2025 at 5:08 PM
migrate 99% of your components automatically.
Internally, this change allowed for deep optimizations in the framework, resulting in better performance, stability and less complexity (easier to maintain + contribute).
Read the full release notes here:
docs.jaspr.site/releases/v/0...
Internally, this change allowed for deep optimizations in the framework, resulting in better performance, stability and less complexity (easier to maintain + contribute).
Read the full release notes here:
docs.jaspr.site/releases/v/0...
Build methods now return a single Component (instead of an Iterable).
This makes it even easier and more familiar to write Jaspr components. If you still want to return multiple children, use fragment().
Don't worry about migration. The new 'jaspr migrate' command will ->
This makes it even easier and more familiar to write Jaspr components. If you still want to return multiple children, use fragment().
Don't worry about migration. The new 'jaspr migrate' command will ->
September 13, 2025 at 5:08 PM
Build methods now return a single Component (instead of an Iterable).
This makes it even easier and more familiar to write Jaspr components. If you still want to return multiple children, use fragment().
Don't worry about migration. The new 'jaspr migrate' command will ->
This makes it even easier and more familiar to write Jaspr components. If you still want to return multiple children, use fragment().
Don't worry about migration. The new 'jaspr migrate' command will ->