This repository was archived by the owner on Oct 24, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 90
Build breaks when using linear-gradient #98
Comments
JayCanuck
added a commit
to enactjs/cli
that referenced
this issue
Oct 23, 2018
From your output, there's indeed a syntax error in the CSS, missing a closing parenthesis: -webkit-gradient(linear, left top, right top, from(currentColor), color-stop(0%, transparent); |
Yes, this is because of the custom properties transpiling mentioned in my last comment. See also the links I‘ve referenced there. No problem. :D Edit, to clarify: The CSS is built from a SCSS source (linked in my initial post) and then transformed/transpiled with PostCSS. |
@mserajnik Oops, yeah sorry... |
This has been fixed in PostCSS Custom Properties v8.0.9 and published in PostCSS Preset Env v6.3.1. 🎉 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm using Plyr in one of my projects. Plyr uses
linear-gradient
, which seems to be causing issues when building with postcss-preset-env enabled, in particular the following occurence: https://github.com/sampotts/plyr/blob/3a8332bdb30e1f64047a0f8a3e60647f0473301b/src/sass/components/sliders.scss#L22-L26When building, it fails with the following error:
When I disable postcss-preset-env and build without it, it works fine.
I understand that you are mainly combining several other tools in one package and that the issue should lie within one of those tools. I am positive that this was not an issue in
6.0.7
, so some change between that release and6.2.0
might've broken it. I'm using the default configuration:The Browserslist configuration is the following:
I was assuming that the issue would be autoprefixer, but using it directly instead of postcss-preset-env works fine.
You can find an example here: https://github.com/mserajnik/postcss-preset-env-linear-gradient-issue
Just run
yarn
andyarn build
and you can see the build breaking.The text was updated successfully, but these errors were encountered: