The journey to Preact X began on a quiet evening in October 2017. Since then, more than 100 people have helped shape the future of this project and community. We're beyond excited to finally share the result of this multi-year effort with everyone. ⚛️ https://t.co/pfElUc971H

Now that @preactjs is so back, here's a blog post I wrote about its internals and how massively efficient it is

I am working in something *very* wild for Preact, which I believe will be a complete game changer. Actually I'm on vacation BUT when I get back I will continue working on this *very* wild thing. 6 year old idea but the last 2 years of Preact features make it infinitely better.

@jexia_ I just rebuilt https://t.co/jOiDi1yT6Y with Preact. It was bliss. I’m loading it via import maps from the browser because Preact actually ships ESM! Unlike React that doesn’t even ship a file you can use in a browser. 🙈

Seeing Preact evolve from the 300k weekly downloads in May 2020 to the 6M we have today has been quite a journey. Thank you to everyone supporting us!

Holy shit, Preact

@mjackson @branmcconnell @abarreraaponte Since the launch of signals, I think you'll find a lot more Preact users are authoring class components again (I certainly am). Ergonomics are pretty darn good: https://t.co/eJ5KFuFh3Y Not that you have to support them, but they're far from dead.

Preact Signals just got a huge perf boost: 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 @JoviDeC for making this happen.

New @preactjs blog post from @barelyreaper! Demystifying how island architecture works and being able to setup your own, using tools you already have around you. https://t.co/o7IZA8rAqs

Preact X, a story of stability. https://t.co/PgExCUdX53

@slightlycode @ImSh4yy Yeah, all of checkout is Preact.

🚦 Now that we shipping Preact signals integration for Lit with the @ lit-labs/preact-signals package, would anyone be interested in an Angular Signals integration? See a demo on the https://t.co/dWGUAP2IVK playground: https://t.co/ePfuh36FyA

For the curious: Here is how you'd do <input bind:value={signal}> in Preact. Thanks to @preactjs 's options plugin API this is pretty easy to add on the fly. https://t.co/LcpeWBlvOP

Got custom renderers working in @preactjs by implementing react-reconciler via option hooks. Here's react-three-fiber running in Preact, demo here: https://t.co/aO1TSa4QFI. I've released this under 0.x as the very creatively named preact-reconciler: https://t.co/4BVXqkKTlf.

Next version of @preactjs DevTools will display which exact hook caused a component to update. Previously it would just display "Hooks changed" and not say which of them did.

The navigation on the @Apple site is built with Preact!

Getting React Spring to work with @preactjs was effortless! Now I can build more of those little and lovely details, making UI and UX more fun.

Thank you for your donation @airbnbeng 🙏 Your contribution makes a difference! https://t.co/KA5biMVcxX

@preactjs 10.11.1 is out now 🎉 - 📶 Updates DOM+SVG types for signals - ♻️ Only remove nested DOM nodes when necessary - 📦 Update preact/compat export map - 📨 Fix unable to set data-* attributes to "false" - 🧽 Usual round of bug fixes... https://t.co/Xgc7kHg5Vy

So @jviide, who is a wizard, rewrote Signals' reactivity implementation and it's now absurdly fast, and effectively memory-stable.

Today we are releasing Preact 10.11.0 and among various fixes and maintenance we have a new hook "useId"! You can now generate unique consistent identifiers! Demo: https://t.co/bDhRklehFW Little writeup because I really loved working on this