Closed xavortm closed 2 years ago
@xavortm can you try with 10up-toolkit v2 that has just been released?
I am having a similar issue and using v2 does not resolve it.
I was able to solve this on my project by:
npm i postcss
in the /wp-content
directoryIt seems there is a bug with Postcss v8.4.4 and some linting tools. In my case it was either:
Forcing the most recent Postcss seemed to correct the problem.
Thanks @gthayer . Looks like we can just update postcss to the latest version in 10up-toolkit to mitigate this problem.
Additionally, this might be already a non-issue for most users as new install of 10up-toolkit would already install the latest postcss version.
Fixed in #135
Describe the bug
Running linting in a project outputs the following error:
After searching for what is the case, I found this issue: https://github.com/stylelint/stylelint/issues/5766 and it seems that updating the postCSS version should fix it.
Steps to Reproduce I can't confirm if the steps would work as I am working on a new project that uses "10up-toolkit": "^1.0.0".
Expected behavior
No errors;
Screenshots
Environment information
WordPress information M/A
Additional context