Replies: 1 comment
-
The If you are trying to use v3, ensure the version qualifier is used: $ npm install -D tailwindcss@3 postcss autoprefixer
$ npx tailwindcss init -p |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
❓ Problem
I'm setting up Tailwind CSS on Windows 11, and after installing Tailwind via:
the CLI installation succeeds, but running:
produces this error:
No stack trace is shown other than a log file reference.
🛠 Environment
✅ What I’ve Tried
Renamed folder to remove spaces (
js simple
➝js-simple
)Deleted
node_modules/
,package.json
,package-lock.json
, and re-rannpm init
and reinstallCleared
npm cache clean --force
Tried running binary manually:
→ Triggers “not recognized” error
Attempted fallback paths:
→ Same failure
Verified Node and npm versions and reinstalled Node.js fresh
❔ Questions
What could cause
npx
to fail to detect the Tailwind executable even when installed?Is this a bug in
npx
on Windows or a Tailwind packaging issue?Are there recommended workarounds to initialize Tailwind without
npx
?Any debugging steps to pinpoint why the binary isn’t being generated?
Beta Was this translation helpful? Give feedback.
All reactions