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
See original GitHub issuePostCSS 8 was released. It has no breaking changes related to rollup-plugin-postcss, most of changes are for plugins. Full changelog.
- Move
postcsstopeerDependencies - Update
postcssversion
Issue Analytics
- State:
- Created 3 years ago
- Reactions:26
- Comments:7 (1 by maintainers)
Top Results From Across the Web
PostCSS 8 for end users - GitHub
PostCSS 8 supports plugins from PostCSS 7. You just need to update postcss dependency and tool, which run postcss (like postcss-loader or ...
Read more >PostCSS 8.0: Plugin migration guide - Evil Martians
PostCSS 8.0 : Plugin migration guide · Step 1: Move postcss to peerDependencies · Step 2: Use the updated API · Step 3:...
Read more >postcss - npm
PostCSS is a tool for transforming styles with JS plugins. These plugins can lint your CSS, support variables and mixins, transpile future ...
Read more >Error: Please install PostCSS 8 or above. how can I fix this?
Here is the dependency file that I installed. and It shows me Pleaseenter image description here install PostCSS 8 or above.
Read more >Storybook Addon PostCSS
Storybook addon used to run the PostCSS preprocessor against your stories. ... and create a PostCSS config in the base of your project,...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
If you want to get this early, I pushed a fork:
🎉 This issue has been resolved in version 4.0.0 🎉
The release is available on:
Your semantic-release bot 📦🚀