Error: Use process(css).then(cb) to work with async plugins (RN 0.72.X)

[Cnordbo]

Describe the bug
Nativewind/babel - Complaining about async plugin after updating to version 0.72.X

Exact error:

Use process(css).then(cb) to work with async plugins

To Reproduce
Steps to reproduce the behavior:

1. Setup a new react-native project using the CLI v0.72.X (npx react-native init nativewindTest)
2. Set up nativewind according to the docs
3. See error

Expected behavior
Expected the app to load with styling

Screenshots

Additional context
Occured after upgrading from 0.71.X to 0.72.X

Stack traces are inconsistent in how they show up, so i was unable to get a full stack trace during the test project. But the issue seems to be related to how postcss is used.

[dylanmeivis]

@Cnordbo I'm having the same issue at the moment. If you find a fix in the meantime could you please let us know here?

[amireds]

Experiencing same issue here as well...

[marklawlor]

Tailwindcss published a breaking change as a minor version. Please lock your tailwindcss@3.3.2

[dylanmeivis]

Can confirm this fixed it for me, thanks @marklawlor !

[amireds]

Tailwindcss published a breaking change as a minor version. Please lock your tailwindcss@3.3.2.

It worked for me... Thanks @marklawlor

[Cnordbo]

Worked for me as well! Thanks a lot @marklawlor :)

[Daniel-MSoares]

It Worked for me as well! Thanks a lot @marklawlor :)

[JClackett]

Still having the same issue, expo 48, tailwind 3.3.2?

Use process(css).then(cb) to work with async plugins

Failing to build on expo

[akinadebowale]

Issue persists on RN CLI @marklawlor. Tried yarn add --dev tailwindcss@3.3.2.

[marklawlor]

If your still having this issue, then you should manually check inside your node_modules at the package.json version of tailwindcss and use commands like npm list tailwindcss to ensure you don't have multiple versions installed.

If you still have the issue after manual verification then provide a link to your repo.

[akinadebowale]

Thanks @marklawlor. After doing some digging and testing, seems the issue on end was cache related. Did some deep cleaning, re-installed everything, and now it working correctly.