-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
postcss v8.2.12 fails to build (Nuxt) #2182
Comments
I'm using |
I fixed it by linking the css by cdn on head in nuxt.config.json instead of linking css through the css linker. here is my solution using app.html so we can defer loading and improve performance
|
But that just removes the verification, doesn't it? |
yep, postcss won't touch the css. if you need it up and running quickly its a solution. though I understand not ideal, but hey, deferring a CDN css is not that bad, i've had issues like this one with the css sometimes with plyr, so im going this route for now, less headaches. |
I have exactly the same issue without Nuxt, just with Webpack. Downgrading from 3.6.7 to 3.6.4 fixes the issue. |
same here |
it is because one of the "+ - *" signs in the css, the difference between v3.6.4 and v3.6.7 v3.6.4 margin-right:calc((calc(var(--plyr-control-spacing,10px) * .7) - 2) * -1); v3.6.7 margin-right:calc(var(--plyr-control-spacing, 10px)*.7*-1 - -2); |
I did some further research and it looks like this issue's root is csstools/postcss-preset-env#191. Closing this one. Further explanation: plyr generates its CSS using PostCSS 8 and Nuxt does not fully support PostCSS 8 yet. |
For all Googlers - you can use PostCSS8 with nuxt now via https://github.com/nuxt/postcss8 |
This issue is similar to #2174, duplicating redxtech/vue-plyr#359 (comment):
Expected behaviour
postcss v8.2.12 does not throw an error.
Actual behaviour
postcss v8.2.12 does not throws an error.
Steps to reproduce
Build this branch: dargmuesli/creal#93
Environment
https://github.com/dargmuesli/creal/blob/master/Dockerfile
Console errors (if any)
See this build log.
The text was updated successfully, but these errors were encountered: