in the next version of tamagui
web averages ~half the classnames and we get perfect RN text semantics + full flattening optimization thanks to CSS "@scope () to ()"
Tamagui is now the only way to have perfect cross-platform animations, but fully shared:
animations-motion:
butter smooth spring animations on web
even at high CPU usage
animations-reanimated:
the best animation driver for native
now 0-rerenders + worklets
If you want to work with some of the most caring developers, who can deliver both inspiring design and technical excellence, we're exploring consulting this year as well:
addeven.com
We've got a few more nice announcements to make over the next weeks, as well as a lot more to show in v2. Look out for that!
We've been quiet for a long time, only because our teams been working extremely hard trying to build out the future of universal apps.
.... that means for example that the completely re-written Sheet component now feels as good as any Sheet you've tried.
Seamless scroll-to-drag handoff, seamless keyboard integration, and seamless calculation of safe areas.
@tamagui/native is here and brings integration with native deps.
Collect them like Pokémon and as you plug them in, they gracefully enhance everything, we have:
- react-native-safe-insets
- react-native-gesture-handler
- react-native-keyboard-controller
- react-native-teleport
There's too much to share, some highlights...
🧈 Motion driver for web
+ Tamagui now has "0️⃣ re-render" internals for all internally driver animations - media query, pseudo style, group style, you name it.
The combination is incredible, completely off-thread spring animations.
Didn't like part of Tamagui before?
We fixed it.
Wish we had a feature?
We have it.
v2 is about bringing Tamagui from "does everything, some well" to "does everything, well"
500+ new tests 🆙
Redone docs 🆙
Native integrations 🆙
Ease-of-install🆙
tamagui.dev/blog/version-two
As a result of this and other security vulnerabilities, we're going to completely strict package versions in version 2. This was a patch-version change which is especially concerning.
We highly recommend you disable running postinstall scripts by default as well.
It seems so far only one person in our community was affected, which is good news as we've checked quite a few machines already.
It also seems to not be the most aggressive malware, without any crypto, browser control, or deep secrets exploration, it only finds ENV
That said please do check your system. If you use bun or a pm that doesn't run postinstall scripts you are more protected.
You can check ~/.yarn/berry/cache for kill-port- and see if its above 2.0.1 which may indicate you're affected
There's more instructions in the blog post