You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm the author of an asset pipeline for PHP (http://github.com/CHH/pipe). For tool support it would be nice if yuglify would support piping JS/CSS into STDIN, and then outputting the minified code to STDOUT — just like the underlying uglifyjs.
An asset pipeline, has a filter pipeline where the output from the last filter gets put into the next filter. When using yuglifyjs in it's current state in a such filter pipeline, the tool needs to write the input data to a temporary file, and read the output back from another temporary file, which is cumbersome to use.
Switching between CSS and JS compression could be done via a flag, for example --css and --js.
I wasn't planning on adding a "nice" cli option for this since it was primarily used as a node dependency, but I'll look into this today and get at least this added..
I'm the author of an asset pipeline for PHP (http://github.com/CHH/pipe). For tool support it would be nice if
yuglify
would support piping JS/CSS intoSTDIN
, and then outputting the minified code toSTDOUT
— just like the underlyinguglifyjs
.An asset pipeline, has a filter pipeline where the output from the last filter gets put into the next filter. When using
yuglifyjs
in it's current state in a such filter pipeline, the tool needs to write the input data to a temporary file, and read the output back from another temporary file, which is cumbersome to use.Switching between CSS and JS compression could be done via a flag, for example
--css
and--js
.Example:
The text was updated successfully, but these errors were encountered: