CLI init forces tailwind.config.js, but Uniwind projects don’t use one (CSS-first)

[Dellybro]

I’m using Uniwind (latest), which is CSS-first and explicitly does not require a tailwind.config.js (theme/config lives in global.css).

When I run the React Native Reusables CLI (init / scaffolding), it prompts me to create a tailwind.config.js. I’m not using tailwind.config.js in my Uniwind setup and I don’t want to add one just to satisfy the CLI.

React Native Reusables is documented as NativeWind-based, and the CLI seems to assume a Tailwind v3-style config file exists.
GitHub

Steps to reproduce

Create a React Native app using Uniwind (CSS entry file + withUniwindConfig in metro.config.js)

Run:

npx @react-native-reusables/cli@latest init (or similar)

CLI prompts for / requires tailwind.config.js

Expected behavior

CLI should support Uniwind’s config-less workflow: Don’t require tailwind.config.js, or Provide a flag like --skip-tailwind-config, or Detect Uniwind and proceed using global.css + Uniwind config (from metro.config.js)

Actual behavior

CLI blocks or guides me toward adding tailwind.config.js, which conflicts with Uniwind’s recommended setup.

Why this matters

Uniwind explicitly supports removing tailwind.config.js and moving theme/config to CSS.
Uniwind

Forcing a JS config file is friction and makes Uniwind setups feel unsupported.

Possible implementation idea

Detect Uniwind by parsing metro.config.js for withUniwindConfig(...) and/or the configured dtsFile (some setups don’t keep it at the repo root). There’s already a related CLI detection issue about this.
GitHub

If Uniwind is detected, skip Tailwind-config steps and proceed with Uniwind defaults.

[radithyaa]

Yes, reusable RN should start supporting Tailwind v4 right now.

[azezsan]

need clarification from the maintainers, same with tailwind v4 on nativewind is that supported?

[Dellybro]

Soo any updates on this?