Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

PostCSS 8 Support

See original GitHub issue

What problem does this feature solve?

This feature solves compatibility issues with multiple frameworks such as Tailwind v2.0 (https://tailwindcss.com/docs/installation#post-css-7-compatibility-build). Currently, the lock file shows that postcss7 is required, which generates issues when trying to build with webpack using tailwind css framework.

What does the proposed API look like?

upgrade in yarn.lock:

"@vue/component-compiler-utils@^3.1.0":
  version "3.1.1"
  resolved "https://registry.yarnpkg.com/@vue/component-compiler-utils/-/component-compiler-utils-3.1.1.tgz#d4ef8f80292674044ad6211e336a302e4d2a6575"
  integrity sha512- lN3nsfJJDGMNz7fCpcoYIORrXo0K3OTsdr8jCM7FuqdI4 70TY6gxY6viJ2Xi1clqyPg7LpeOWwjF31vSMmUw==
  dependencies:
    consolidate "^0.15.1"
    hash-sum "^1.0.2"
    lru-cache "^4.1.2"
    merge-source-map "^1.1.0"
    postcss "^7.0.14"
    postcss-selector-parser "^6.0.2"
    prettier "^1.18.2"
    source-map "~0.6.1"
    vue-template-es2015-compiler "^1.9.0"

To support PostCSS 8.

Issue Analytics

State:
Created 3 years ago
Reactions:8
Comments:8 (3 by maintainers)

Top GitHub Comments

24reactions

joshjecommented, May 18, 2021

I’d like to add that the version of postcss in this repo has two known vulnerabilities:

https://snyk.io/vuln/SNYK-JS-POSTCSS-1255640 - Affecting postcss package, versions <8.2.13
https://snyk.io/vuln/SNYK-JS-POSTCSS-1090595 - Affecting postcss package, versions >=7.0.0 <8.2.10

Any chance of upgrading it to 8?

1reaction

sodateacommented, Feb 22, 2021

which generates issues when trying to build with webpack using tailwind css framework.

What issues? Could you elaborate? Because the postcss 7 listed here is only used for scoped styles, and tailwind is expected to be executed in another pipeline, they shall not interfere with each other.