You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Natiwind styles using pnpm do not work. Tailwind does #268
Yeah AFAIK pnpm has never worked with RN let alone Nativewind.
I think the Solito starter is now outdated for use with Nativewind (or requires version locking to previous version, I'm not sure).
But it's a useful reference because 1) it uses Yarn for the monorepo (with nodeLinker: node-modules being mandatory) and 2) it's a working example of RN with Nativewind.
Any updates?
@hknakn It's just a suggestion, but a more helpful post would be about your own experiences, such as:
"I couldn't get Nativewind working with pnpm either. My version numbers are Tailwind _, Expo _, RN _, Nativewind _, and PNPM _. Has anyone else seen this issue or have any recommendations?"
Again I must stress that unless you read in recent Expo docs that PNPM actually works with Expo + RN, then I would abandon it in favor of either a Yarn monorepo or separate apps.
Closing as stale — no reproduction provided. pnpm compatibility issues are typically resolved via hoisting configuration. If still relevant, please open a new issue with a repro.
Activity
DoctorDerek commentedon Jul 9, 2025
Yeah AFAIK pnpm has never worked with RN let alone Nativewind.
I think the Solito starter is now outdated for use with Nativewind (or requires version locking to previous version, I'm not sure).
But it's a useful reference because 1) it uses Yarn for the monorepo (with
nodeLinker: node-modulesbeing mandatory) and 2) it's a working example of RN with Nativewind.@hknakn It's just a suggestion, but a more helpful post would be about your own experiences, such as:
Maybe my most recent article would be helpful in clarifying the various RN Expo Nativewind issues that are inevitable in this development environment. Cheers! https://medium.com/react-in-the-real-world/react-native-isnt-perfect-but-i-still-recommend-it-here-s-why-9f9b2ce0911b?sk=07dcd1305bf7dd4b9695178e7ead5c87
DoctorDerek commentedon Jul 9, 2025
Solito / Nativewind starter code: https://github.com/nandorojo/solito/tree/master/example-monorepos/with-tailwind
Solito / Nativewind starter docs: https://solito.dev/tailwind
Most recent update about Nativewind in Solito repo: nandorojo/solito#448
That post links to: https://github.com/SantiMNV/solito-nativewind-v4-app-router
DoctorDerek commentedon Jul 9, 2025
Also unclosed PR nandorojo/solito#506 may indicate how to use Nativewind 4.
Again I must stress that unless you read in recent Expo docs that PNPM actually works with Expo + RN, then I would abandon it in favor of either a Yarn monorepo or separate apps.
francois-pasquier commentedon Jul 11, 2025
I read all of this.
Expo does work with pnpm
I come from a yarn monorepo. I had issues with it, pnpm worked fine.
The only thing I miss now is a working nativewind install.
Can the maintainers chime in?
a-eid commentedon Jul 18, 2025
it's not working for me either.
a-eid commentedon Jul 18, 2025
@DoctorDerek pnpm works fine with expo... it has been working for us for years.
DoctorDerek commentedon Jul 18, 2025
dannyhw commentedon Jul 23, 2025
@francois-pasquier

you just need to change the content array to actually reference the relative path not the node_modules
note that the web file causes it to crash thats why I specified the paths directly instead of regex
also your nextjs app is not configured to use nativewind so thats why that doesn't work there
chakrihacker commentedon Aug 15, 2025
if you are using bun workspaces try adding this in your metro.config.js
EgorPopovPP commentedon Aug 26, 2025
+1
danstepanov commentedon Oct 15, 2025
@francois-pasquier were you able to implement Danny's suggestion?
francois-pasquier commentedon Oct 15, 2025
Well, listing all the components is tedious imo
It can get quite large as well…
dannyhw commentedon Oct 15, 2025
@francois-pasquier the point is to make the regex match the path more correctly, not to specify each one manually
like
../../packages/app/features/**/*.{js,ts,tsx}francois-pasquier commentedon Oct 15, 2025
Last time I checked doing it this way for packages resulted in a crash
danstepanov commentedon Apr 15, 2026
Closing as stale — no reproduction provided. pnpm compatibility issues are typically resolved via hoisting configuration. If still relevant, please open a new issue with a repro.