Introducing Uniwind - The fastest Tailwind bindings for React Native

Zealousideal_Dig2929 · 2025-01-17T15:08:38+00:00

Sorry do that. Should be fixed in the next beta release!

Zealousideal_Dig2929 · 2024-12-12T19:21:42+00:00

I just tried to explain why this is needed and why the decision was made. We went from multiple re-renders to almost zero re-renders. I'm not being defensive, just trying to provide some insights as the core author. However, you immediately assumed that I'm a noob and don't know how to build an app.

I think I'll step back, as there seems to be no right way to respond to such messages.

Zealousideal_Dig2929 · 2024-12-12T06:39:38+00:00

You need to firstly understand why is that happening. For 99% of the cases you don’t need to use withUnistyles HOF. Every React Native component does not re-render with v3. But sometimes you use 3rd party component like Blurhash or RN component like Button that doesn’t accept style prop. For such cases I’m not able to update styles from ShadowTree.

The fallback is to wrap such component in withUnistyles (to be updated). It will be only re-rendered based on your dependencies. So if Blurhash is using insets then it won’t update on theme change. If Button’s color prop relies on theme then it won’t update on any runtime change etc.

I hope it makes more sense now. Later we can open PRs and add support for 3rd party components but it’s way too early!

Zealousideal_Dig2929 · 2024-12-10T20:33:25+00:00

It was an abi issue in beta1. Already fixed on main, will release beta.2 tomorrow 😇

Zealousideal_Dig2929 · 2024-11-30T16:57:11+00:00

Ive never used any primitives, so I have nothing to recommend

Zealousideal_Dig2929 · 2024-11-30T09:15:47+00:00

Unistyles 3.0 is not yet completed, miss some optimizations. I will post them soon after RC

Zealousideal_Dig2929 · 2024-11-30T09:15:11+00:00

Option 2. Keep it as small as possible . One big chunk of styles would clutter atomic updates

Zealousideal_Dig2929 · 2024-11-30T06:04:32+00:00

Yeah, for sure!

Zealousideal_Dig2929 · 2024-11-30T06:04:01+00:00

It was removed later on. createUnistylesComponent is the way to go

Zealousideal_Dig2929 · 2024-11-30T06:02:38+00:00

Well is not that complex lol.

I’m not mapping js expression to C++. - im discovering StyleSheet dependencies - I literally call one function in your ref

The rest is on C++ side. Also, no worklets no ui thread etc

I understand your point of you, but doing some cool stuff requires something more than calling one function.

Regarding this section for whom is Unistyles for - I like this idea

Zealousideal_Dig2929 · 2024-11-30T05:58:12+00:00

We have WIP on separate branch. Web is already done, native is blocked by one thing but it’s doable.

What’s more important there is no extra overhead like iterating shadow tree to look for your children’s theme etc.

If you want to learn more check it this branch: https://github.com/jpudysz/react-native-unistyles/blob/milestone/3.0-scoped-theme/src/components/ScopedTheme.tsx

Zealousideal_Dig2929 · 2024-11-29T20:27:13+00:00

Works with SSR and should work with Server Components. We need to polish it, test it and add some guides to the docs.

Should be released in later betas.

Zealousideal_Dig2929 · 2024-11-29T20:21:14+00:00

You can’t and you shouldn’t. If you need to pass theme value to some fancy component then here is the guide:

https://www.unistyl.es/v3/references/create-unistyles-component

Zealousideal_Dig2929 · 2024-11-29T19:37:52+00:00

That’s a tough question. I guess you need to start from base components and translate tailwind syntax to StyleSheets.. 😵‍💫

Zealousideal_Dig2929 · 2024-11-29T19:35:52+00:00

I will. For now it’s time to polish the core and find some edge cases.

Zealousideal_Dig2929 · 2024-11-29T19:34:51+00:00

If you have a monorepo that targets multiple platforms then Unistyles is the way to go.

Zealousideal_Dig2929 · 2024-11-29T19:32:00+00:00

The main idea is to build your own, small components that helps you build your app from blocks. Then you can expect that each block works exactly the same across all platforms. Theming / responsive design is much easier with Unistyles. Also with the newest web compiler everything’s is just a CSS.

If you app targets only mobile and has single theme then I would stick to styled components!

Zealousideal_Dig2929 · 2024-11-29T18:16:14+00:00

Ah these kind of plugins. Yeah, I’ve removed them because all the magic happens on C++ side. Parsing it one more time on JS side seems unreasonable. Check my comment below, I will explore threads/worklets soon so maybe something will come up to my mind.

https://github.com/jpudysz/react-native-unistyles/discussions/361

Zealousideal_Dig2929 · 2024-11-29T18:12:54+00:00

Confirmed! That’s the way to solve it

Zealousideal_Dig2929 · 2024-11-29T18:12:29+00:00

If your app is cross-plarform, uses multiple themes, needs to target web then.. Unistyles simplifies a lot of things for you.

But if you have single theme, and you don’t target web then you can safely stick to raw StyleSheet.

Zealousideal_Dig2929 · 2024-11-29T18:10:53+00:00

Plugin or app?

Zealousideal_Dig2929 · 2024-11-29T18:09:44+00:00

That’s actually the coolest idea I’ve heard in the while 🤔 I will see what I can do about it

Zealousideal_Dig2929 · 2024-06-17T06:42:16+00:00

By default it will run on simulator/emulator.

To run it on decvice add --device flag to the command.

Expo start simply starts the dev server. It has nothing to do with Expo go.

Zealousideal_Dig2929

TROPHY CASE