Catch the Tamagui talk at @appjsconf
It was an honor be a speaker and really felt the love, so many great speakers and super talented people there!
youtube.com/watch?v=1WnmFqIm…
@natebirdman giving a deep dive into @tamagui_js at @appjsconf. As a very early adopter, I highly recommend it as it’s one of my favorite libs! Well taught piece of software by a talented dev spending thousands of hours to build this! Will share a video soon!
We're making a new guide: How to Build a Button.
On the flight to @appjsconf, @natebirdman got 4 new features working to simplify the code into what we've been wanting for months.
It's 💦
Can you spot the 2 more obvious ones and 1 less obvious one shown here?
Ok, so going to go with Button* since it autocompletes better and the namespace makes sense (it’s a part of the Button family more than headless).
So let’s try again.
Case for ButtonHeadless: VSCode autocomplete will show it as you type Button for easier discoverability, and it keeps Button* things within a namespace.
Case for HeadlessButton: reads more naturally, and it keeps headless things in a namespace.
Trying to support type: "module" / fully specified imports / mjs has been a nightmare.
Latest @tamagui_js release finally removes the last remnants of it. What a shit-show.
Making onboarding easier one day at a time 🌅 this morning we've added a new starter `simple-web`
Just run `npm create tamagui@latest`
✅Complete tamagui.config.ts from scratch
✅Webpack and vite
✅No monorepo
We still recommend using the `next-expo-solito` starter or at least the `themes` package for a more full-featured prod-ready setup.
But this starter is great for playing with Tamagui quickly, learning how to configure it, and understanding the basic design system definition.
Three nice animations improvements:
🔸 Animations now have full SSR support even using spring based animation drivers with themes
🔸 @tamagui/react-native-animated driver supports all style values including color values
🔸 @tamagui/moti-driver is available for testing