CLI on Windows runs detached if TTY is not detected? #17371
Unanswered
NotJustAnna
asked this question in
Help
Replies: 0 comments
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.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello! TS/Java dev here trying to use TailwindCSS!
I don't know if I'm doing something wrong. I'm trying to run Tailwind on a Gradle project and AFAIK the CLI spawns a new detached process and exits with zero. Half of the time this means that I end up with an empty css file when creating the final jar file.
Below is my Gradle's run, cleaned up a bit for help. Tailwind CLI apparently breaks away from Yarn and concurrently runs parallel to the rest of the execution...
I am doing something wrong? I don't seem to be able to reproduce this behaviour when running on my terminal. Or is this a bug?
So far I've tried:
node node_modules/@tailwindcss/cli/dist/index.mjs
All cases it detaches.
Tried Node.js v18.17.1 and v22.14.0
If I run it with a script, eg.
"run-tailwind": "ping localhost -n 1 && yarn tailwindcss -o index.css && ping localhost -n 1"
, it detaches between the pings.Beta Was this translation helpful? Give feedback.
All reactions