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
feat: add back postcss-preset-env
#18704
Conversation
Co-authored-by: Renovate Bot <bot@renovateapp.com>
Co-authored-by: pooya parsa <pyapar@gmail.com>
Co-authored-by: Renovate Bot <bot@renovateapp.com>
Co-authored-by: pooya parsa <pyapar@gmail.com>
[release] resolves nuxt/framework#494
* chore: update logo * chore: update link to community
Co-authored-by: Pooya Parsa <pyapar@gmail.com>
Open in CodeSandbox Web Editor | VS Code | VS Code Insiders |
Codecov ReportBase: 65.19% // Head: 66.55% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## 2.x #18704 +/- ##
==========================================
+ Coverage 65.19% 66.55% +1.35%
==========================================
Files 94 93 -1
Lines 4155 4075 -80
Branches 1172 1149 -23
==========================================
+ Hits 2709 2712 +3
+ Misses 1167 1103 -64
+ Partials 279 260 -19
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work on adding back compatibility with env. since we are introducing other breaking changes anyway in 2.16, postcss8 shouldn’t be a problem.
We need to test edge against tailwindcss module. |
📚 Description
This PR updates #9671 to add back
postcss-preset-env
, which is now updated for PostCSS8. This reduces the breaking change surface of the linked PR.We might also consider reverting the breaking changes to postcss options in order to make this more manageable as a migration step. What do you think @pi0 - is there a reason we need to make the following change?
build.postcss
has been moved to postss-loader options format:build.postcss.plugins
tobuild.postcss.postcssOptions.plugins
, the object format is still samebuild.postcss.order
tobuild.postcss.postcssOptions.order
Note: to reduce the clutter of commits this is marked as a PR against
2.x
but before merge I will update to merge into #9671 and thence into2.x
.