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
Hi, I just submitted another issue which occurred under the same conditions: #1246 So there could be a relation, but I think the issues are separate, so thought starting a new ticket would be best. Apologies if not.
I'm using the latest gulp-clean-css (4.3.0) which I believe is a wrapper for clean-css.
I'm seeing a rogue % symbol added to a property value. It means the generated CSS is invalid. It's easiest to demonstrate with the example below. In fairness, there's a fair bit going on with css variables used within each other, so I'm not surprised that something in the chain couldn't understand it.
I read somewhere that it could be getting confused between the SASS hsl function and CSS hsl declaration and that a solution was to use HSL (uppercase). This has the same result (which I guess makes sense as it seems to be a cleaning issue rather than an SCSS generation issue. Removing the clean step in the pipeline resolves the problem. Interestingly, though changing to hsla does resolve the problem. So for the moment, I can get around the issue with that.
Other than that, the only solution I've found it to change the optimisation level to 0, but that removes a lot of other nice stuff.
Environment
clean-css version - npm ls clean-css: gulp-clean-css is 4.3.0
Hi, I just submitted another issue which occurred under the same conditions: #1246 So there could be a relation, but I think the issues are separate, so thought starting a new ticket would be best. Apologies if not.
I'm using the latest gulp-clean-css (4.3.0) which I believe is a wrapper for clean-css.
I'm seeing a rogue
%
symbol added to a property value. It means the generated CSS is invalid. It's easiest to demonstrate with the example below. In fairness, there's a fair bit going on with css variables used within each other, so I'm not surprised that something in the chain couldn't understand it.I read somewhere that it could be getting confused between the SASS
hsl
function and CSShsl
declaration and that a solution was to useHSL
(uppercase). This has the same result (which I guess makes sense as it seems to be a cleaning issue rather than an SCSS generation issue. Removing the clean step in the pipeline resolves the problem. Interestingly, though changing tohsla
does resolve the problem. So for the moment, I can get around the issue with that.Other than that, the only solution I've found it to change the optimisation level to 0, but that removes a lot of other nice stuff.
Environment
npm ls clean-css
: gulp-clean-css is 4.3.0node -v
: v16.14.2Configuration options
My gulp task is very simple, like this:
For the options, I've tried playing with many options but the default no-options produces the error.
Input CSS
Actual output CSS
Expected output CSS
If I'm doing something wrong, I'm sorry and any help would be greatly appreciated.
The text was updated successfully, but these errors were encountered: