What version of Tailwind CSS are you using?
v4.2.0 or above
What build tool (or framework if it abstracts the build tool) are you using?
Tailwind CLI
What version of Node.js are you using?
N/A
What browser are you using?
N/A
What operating system are you using?
Windows 10
Describe your issue
I've set up Tailwind CLI 4.2.0 to be run every time I update any of our Tailwind-enabled CSS-files in the JetBrains IDE.
This is what's running and the output:
C:\htdocs\tailwindcss.exe --input C:\htdocs\beta\files\beta\tailwind.css --output C:\htdocs\beta\files\beta/../../static/beta/css/tailwind.css --optimize --cwd C:\htdocs\
≈ tailwindcss v4.2.0
Process finished with exit code 1
"exit code 1" is seldom good news..
If I downgrade to Tailwind CLI 4.1.18, then the program successfully exits.
c:\htdocs>C:\htdocs\tailwindcss.exe --input C:\htdocs\beta\files\beta\tailwind.css --output C:\htdocs\beta\files\beta/../../static/beta/css/tailwind.css --optimize --cwd C:\htdocs\
≈ tailwindcss v4.1.18
Done in 1s
Would it be possible to revert to the old (<4.2.0) way of exiting the CLI, or is the problem on how the "/" and "" are used interchangably in the input and output arguments? I saw no mentions of it in the changelog.
What version of Tailwind CSS are you using?
v4.2.0 or above
What build tool (or framework if it abstracts the build tool) are you using?
Tailwind CLI
What version of Node.js are you using?
N/A
What browser are you using?
N/A
What operating system are you using?
Windows 10
Describe your issue
I've set up Tailwind CLI 4.2.0 to be run every time I update any of our Tailwind-enabled CSS-files in the JetBrains IDE.
This is what's running and the output:
"exit code 1" is seldom good news..
If I downgrade to Tailwind CLI 4.1.18, then the program successfully exits.
Would it be possible to revert to the old (<4.2.0) way of exiting the CLI, or is the problem on how the "/" and "" are used interchangably in the
inputandoutputarguments? I saw no mentions of it in the changelog.