Supports Tailwind CSS v4.0 #1422

Any updates?

None of these timelines are promises and should not be taken as such. v5 will be ready when it is ready. Open source contribution is welcome.

I feel I've been plenty communicative regarding any delays and the reasoning behind them both on GitHub and on the State of Nativewind streams (which are recorded and available on YouTube). I'm not sure to what silence you are referring.

As far as NativewindUI, I'm working on a public changelog system to communicate what's coming down the pipeline.

If you have specific suggestions, I'll take them into consideration.

As far as sponsorships of Zach, Mark, or myself, if you don't agree with something, don't sponsor us.

Thanks for the response.

I understand that timelines are not binding promises, but when they’re shared repeatedly - and missed repeatedly - without clear follow-up in the same places they were first announced (like GitHub), it’s understandable that users feel confused or misled. Not everyone is watching hours of streams or checking YouTube for updates. GitHub is where most of us follow the project’s status.

I’m not questioning your effort or intent (I appreciate the work that goes into both NativeWind and NativeWindUI) but communication means meeting your audience where they are. A short update here when a shared ETA slips would go a long way.

As for sponsorships or purchases, again no issue with those. But when money is involved, the expectations for communication and clarity naturally increase.

Looking forward to the changelog system you mentioned, I think that’s a great step. And I do hope you’ll take this feedback as a signal that the community is engaged and cares about the project.

Thanks again.

@danstepanov anyway any updates about when?

#1422 (comment)

🔥 Never forget the less vocal members of the community who truly appreciate all your efforts! You guys are incredible 🙏

Thanks @CTOverton, really appreciate it. I'm still working to establish the best way to manage a larger/growing OSS library and its community. These comments help remind me of the silent supporters.

I remain open to constructive feedback but I have to be realistic about what I can make time for.

Agreed with CTOverton and jthoward64! Congrats Mark! I'm a dad myself and it's the greatest, most fulfilling, and sometimes stressful adventure lol. The work you guys do is awesome and greatly appreciated. If there are ways I can contribute I'd be happy to do so. Open source only works when all of us work together constructively to make it happen. Negative comments without contributions are an unfortunate fact of people but I think you can safely ignore them and rest easy knowing that there are countless others who greatly appreciate the awesome stuff being built here.

Thanks y'all ❤️

We're moving away from external timeline updates as efforts to keep communicating this set an expectation that doesn't align with the actual nature of the process. Furthermore, these efforts seem to only be met with frustration from the community around work that Mark and I either do for free or that we pay to have done.

Instead, via State of Nativewind, we'll discuss the current challenges/major blockers that we're working through and we'll use the existing release system to communicate major and minor version changes. I'll post the videos here for folks to watch if they'd like more in-depth detail. Lastly, I'll chat with Mark this week about publishing his v5 branch for anyone interested in contributing to the efforts.

The current major blockers are:

1. Replace the existing JSX transform process that adds className to components (backport to v4 as well)
2. Reanimated v4 reaching stability (we're working with the SWM team to ensure this is smooth for v5)
3. Mark is on paternity leave

Teaching the baby to code is week 4 of parenting, is it not? They should be raising PR's in no time

SSR has worked since v1 because on web (the only place SSR exists) it just uses a stylesheet.

SSR has worked since v1 because on web (the only place SSR exists) it just uses a stylesheet.

I used the wrong term. I meant react server components. Currently, you have to use “use client”. “use server” doesn’t work and result in the style being removed

I know “use client” is still SSR, we are missing RSC support though. Any insight on this?

@francois-pasquier based on past experience, I think this experience will get a lot better since they are doing import rewrites (see the migration docs). I'm excited to try this out and see if it improves the integration with RSC-based NextJS

@danstepanov Perhaps unnoticed but the branch is unusable? It's a small shim over react-native-css from looks and "v3" of that does not exist on npm, in the branch or install when running npm install on the branch. I'd love to help test the v5, thanks for all you and Mark's hard work here.

I don't think the branch is supposed to be usable. It's in development. I asked for the branch to be pushed so we could all potentially help with development. I'd ignore the v5 branch unless you're looking to hack on it to move it forward.

https://www.nativewind.dev/v5/getting-started/installation

https://www.nativewind.dev/v5/getting-started/installation

npx rn-new@next --nativewind

https://www.nativewind.dev/blog/v5-migration-guide

but how can i install nativewind v5 now? i searched the versions on npm but didnt find a beta

cause it still not released :)

https://www.nativewind.dev/v5/getting-started/installation

https://www.nativewind.dev/v5/getting-started/installation

https://www.nativewind.dev/v5/getting-started/installation

Isn't that like asking what's the benefit of using Tailwind over just css?

I was thinking more along the lines of "using tailwind alongside react-native-css" vs "using nativewind"