Tailwindcss: Tailwind CLI Build – Output in Shell not file

[patrikkernke]

Tailwind is such a good concept! I love to use it in the future :)
Thanks for your hard work!!

Using Tailwind CLI for simple projects or just giving Tailwind a spin is a great idea too, but it don't work for me. The build command makes the output to the shell, not in a file. The command and file structure is the same like in the documentation.

Is it only on my computer or is it a bug?

[adamwathan]

Hey @patrikkernke! By default it outputs to the shell (in case for whatever absurd reason you wanted to pipe it into something else), but if you provide an output file using the -o flag, it will write the output there.

That said, there was a bug with this command in the 0.1.0 release that caused it to not write the file no matter what. That's been fixed but we haven't published the patch yet. I'll do it now :)

[patrikkernke]

Okay super :) Thank you for the quick reply.

[eduarguz]

oh men, I was wandering around in this for a while, thanks for commenting, to confirm the -o flag didnt work for me either, waiting for the update.

thanks and awesome work

[olakara]

@adamwathan I was hitting my head on this issue!! the output css was always going to console, instead of a file even after giving the -o flag.. Waiting for the update..

[patrikkernke]

I thought it is my npm version or some custom configuration on my computer :)
I am glad that @adamwathan is so quick ;)

[adamwathan]

Sorry for the drama folks! 😄

v0.1.1 is now on npm and should fix this issue 👍

[olakara]

@adamwathan updated my package and was able to create the output file... but CLI still show version 0.1.0 when running tailwind --version.

[patrikkernke]

The output is now correct, for me that is the quickest bugfix in a github repo. From posting it to fix on my computer only 25min :)

Keep on your the amazing work!

[eduarguz]

as the issue is still open, looks like the config file path is not "configurable" or not working on cli
https://github.com/tailwindcss/tailwindcss/blob/8e752f8e3ab8c54e42579764007480a3809ab6d5/src/cli.js#L78

I am not an expert just digging around with some console.log() debugging found that the config wildcard could be accessed using program.args[1].config

can anyone confirm? or am I doing something wrong??

[adamwathan]

@eduarguzher You're right, I am an idiot and should have updated that option at the same time as the output file option 😩 Fixing!

[adamwathan]

This is all fixed up in v0.1.2 👍