Closed danielforsberg closed 9 years ago
I'm not sure if something of the implementation changed with this new release but it has some very bad issues (e.g.: #654)
I'd recommend you to rollback to 3.1.0 (npm i roots@3.1.0 -g
) and stay in there since the 3.2.0 became more stable. Anyway, you could wait for @jenius to shed some light.
Thanks for the tip with the rollback, but wierdly I still get the same result. (Since I already was on 3.1.0
I rolled back to 3.0.0
).
+1
I am getting this same issue. I am on 3.1.0
as well.
This is fixed in commit carrot/roots-css-pipeline@5c588a8b9b23b292f54c7fd89037dd92e127eaf0 (included in v0.3.0 of css-pipeline), so I've found it easiest to just use 0.3.x
as my css-pipeline in my package.json:
"coffee-script": "1.9.x",
"css-pipeline": "0.3.x",
"jade": "1.x",
This produces properly minified css.
Thanks @brewingcode - This resolved the issue
I have an
app.wp.coffee
with:roots compile -e wp
brings all the files where the output is set but the javascript is empty and the css file contains the text[object Object]
This worked before the update to 3.1.0
Thanks