stdin support

[kaihendry]

Could you please support stdin?

$ csslint < /tmp/test.js
csslint: No files specified.

Many thanks

[jklein]

What's the main use case for this? Do you have generated CSS that you want to pipe to csslint? It seems like it should be easy to simply write it to a file and then run csslint on that file.

[pluma]

+1

This is necessary if you want to use CSS pre-processors and don't want the (unmodified) temporary data to hit the disk.

Ideal usage:

$ stylus -p stylesheet.styl | csslint

current usage:

$ stylus -p stylesheet.styl > /tmp/tempfile.css && csslint /tmp/tempfile.css ; rm -f /tmp/tempfile.css

This is suboptimal.

[thom4parisot]

I have opened an issue in parser-lib as it needs to be implemented there before landing in csslint.

[lkraav]

Has anything moved with this?

[steelbrain]

Been open since 2012. Beautiful 👏

[thom4parisot]

@steelbrain not very professional comment :-(

[steelbrain]

@oncletom was in a fun mood, I apologize for the sarcasm.

[steelbrain]

Until this is supported here, I have a PoC CSSLint fork that accepts stdin. You can find it here, I would've opened up a PR with the support myself, but I am a bit busy these days https://github.com/AtomLinter/csslint

[pluma]

I've added a PR that implements this for all three environments. If one of you could check on the Rhino and WSH implementations to make sure they actually work, that might help getting it landed: #605