Big news from the Kuma UI team 🐻❄️
We've started working on crafting the perfect Emotion replacement - exact same syntax, but (nearly) zero-runtime & React Server Component compatible.
More news, including release dates, coming soon. 🚀
Happy to announce that I am officially joining @tamagui_js & @one__js team 🎉✌️
Tamaguiは最適化コンパイラ付きクロスプラットフォームUIライブラリで、OneはReact (Native) + ViteのWeb&モバイルアプリ開発フレームワークです。
日本でReact Nativeをより一層盛り上げていければ嬉しいです🥳
New video 🎬 How to build a smoothly animated table of contents using Framer Motion @framer, Kuma UI @kuma__ui, Zustand, and @pmndrs, by the riverside 🏞️ and a bonfire 🔥 #NeovimInNature
"Deep Dive into TypeScript Parser"
I originally posted this in Japanese, but my friend @astahmer_dev suggested I post it in English, so here it is 😆
https://t.co/BLyKxWGIZu
super interesting article on how the TS parser works ! 🤩
you'll learn why `const a = <T>(b: T) => b;` is seen as a JSX component instead of being parsed as a JS function with a generic
We've submitted the RFC for v2 🐻❄️🎉
✅ Support for variable interpolation in css and styled APIs, just like Emotion.
✅ Dynamic values will now be fully compatible with React Server Components, with minimal runtime intervention.
Let me know your feedback!
https://t.co/akfSw3U94p
✨Happy to see Kuma UI ranked #8 in the Styling / CSS in JS category of the 2023 JavaScript Rising Stars by @michaelrambeau.
Thank you to all our contributors and community members 🐻❄️🫶
https://t.co/WEm2SSwZx7
Hello @nextjs , I've noticed some confusion about CSS-in-JS compatibility with RSC as the doc only mentions Client Component compatibility. Libraries like @panda__css , @tamagui_js and @kuma__ui work just fine with RSC w/o adding 'use client' internally.
https://t.co/oSt4n76pYs
We offer type-safe utility props and theming that impose constraints on design tokens. While we do have attached components, you have the freedom to opt out. Plus, we provide pretty neat documentation that is 100% generated by ChatGPT. 😉
https://t.co/V0zAzs8yQY
What TS-based styling approaches are most similar in DX to Tailwind? I'm looking for:
- No unnecessary naming of things (.my-button)
- Constraints (p-4, p-6 etc)
- No attached component library
- Amazing docs
- Typesafe
- Standard utilities that don't diverge much per project
One reason I love the Utility Props approach used by CSS frameworks like @panda__css and @kuma__ui is that hovering over the props immediately displays information about the CSS property, achieved solely through JSDoc without needing any extra extensions.
I think there's enough space for everyone in the styling ecosystem, everyone has different needs and preferences
I'm glad there are even more awesome alternatives today (Kuma-UI, stylex, css-hooks, tokenami soon)
that being said, I'll definitely root for Panda 😁
Now that Remix supports Vite, Kuma UI is also compatible with Remix! 🎉
We just need to add Server Side Rendering (SSR) support. Stay tuned for updates 🐻❄️
https://t.co/ov6PBWnSuR
📣 One of our maintainers will be presenting at JSConf Japan 2023. Join us for a deep dive into the story behind Kuma UI's creation and our vision for its future 🐻❄️
https://t.co/kpcseJNYxb
I've created an experimental PR to explore the best way to support Server Actions within React Hook Form. Your thoughts and ideas are invaluable, so please provide feedback! 👋
https://t.co/3pDux7TtFx
Lastly, we've introduced a new API, t(), which allows you to use Theme Tokens within `css` and `styled` API!
We'll be updating the documentation soon. Stay tuned! 🐻❄️
https://t.co/AdmwM5ycPv
With our latest release, we've boosted the rendering performance by ~60%! 🎊
We achieved this by optimizing the compiler to transform components into plain HTML + CSS whenever possible.
Could we be the fastest UI component library on the planet? 🌏🐻❄️
https://t.co/j8xOiWGhQv
Additionally, with the support of the community, we've enabled HMR to detect changes in kuma.config.ts !
Now, there's no need to restart the app every time you update the Theme. A big thanks to @jsotakebmx & @kotarella1110 for your contribution! 🙌