I've worked on Preact X for the last 7 years, during which we had a different Preact 11 which was based on long-lived vnodes preactjs.com/blog/preact-x
I've worked on Preact X for the last 7 years, during which we had a different Preact 11 which was based on long-lived vnodes preactjs.com/blog/preact-x
preact/compat code is now tree-shakeable, with representative single-export bundles shrinking by up to ~28%.
Plus: more size wins, better HTML attribute types and maintenance fixes.
This will most likely be the last rc - feedback is appreciated
preact/compat code is now tree-shakeable, with representative single-export bundles shrinking by up to ~28%.
Plus: more size wins, better HTML attribute types and maintenance fixes.
This will most likely be the last rc - feedback is appreciated
Same React app. One is bundled as is.
Another uses preact/compat to alias React imports and swaps in Preact under the hood.
Bundle size (gzip):
React: ~140KB
Preact: ~8KB
All of this by just changing a few lines and installing a couple of packages.
Same React app. One is bundled as is.
Another uses preact/compat to alias React imports and swaps in Preact under the hood.
Bundle size (gzip):
React: ~140KB
Preact: ~8KB
All of this by just changing a few lines and installing a couple of packages.
@preactjs.com is joining the party with an official @tanstack.com Query adapter 🎉
Huge shoutout to @thvdnta.bsky.social, who drove this effort 🙌
Welcome, @preactjs.com 👋
Preact team: Well that just ain’t gonna cut it
Preact team: Well that just ain’t gonna cut it
It's a library that contains tools to test Preact in vitest browser mode.
It's a library that contains tools to test Preact in vitest browser mode.
Go try it out, give feedback and read up on the migration guide at preactjs.com/guide/v11/up...
Go try it out, give feedback and read up on the migration guide at preactjs.com/guide/v11/up...
Signals rendered as text/props & effects only "pull" as fast as needed for rendering. Since computeds run as-needed, they now only re-run as often as their downstream DOM output can be painted.
H/t to @jovidecroock.com for making this happen.
doesn't really affect preact users but will make preact easier to maintain and test once this lands
doesn't really affect preact users but will make preact easier to maintain and test once this lands
And what if Radix itself became 60% smaller? And faster.
What if you could have all of Radix and Preact and a router... for less than half the original size of Radix? or of React?
And what if Radix itself became 60% smaller? And faster.
What if you could have all of Radix and Preact and a router... for less than half the original size of Radix? or of React?
It has quite some history as we first started working on a backing-node (fiber-like) structure for Preact but reversed.
It has quite some history as we first started working on a backing-node (fiber-like) structure for Preact but reversed.
Check it out at github.com/JoviDeCroock...
Check it out at github.com/JoviDeCroock...