chore(devdeps): update dependency postcss to v8.4.4 #964
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
Branch automerge failureThis PR was configured for branch automerge, however this is not possible so it has been raised as a PR instead. |
Codecov Report
@@ Coverage Diff @@
## main #964 +/- ##
=======================================
Coverage 93.05% 93.05%
=======================================
Files 118 118
Lines 3094 3094
Branches 472 472
=======================================
Hits 2879 2879
Misses 161 161
Partials 54 54 Continue to review full report at Codecov.
|
size-limit report 📦
|
scaleway-bot
pushed a commit
that referenced
this pull request
Dec 6, 2021
### [0.126.3](v0.126.2...v0.126.3) (2021-12-06) ### ⚡ Refactor * **theme:** renamed colors into deprecatedColors ([#960](#960)) ([b881213](b881213)) ### 📦 Chore * **devdeps:** update dependency @storybook/testing-react to v1 ([#931](#931)) ([2f50f28](2f50f28)) * **devdeps:** update dependency @svgr/rollup to v6 ([#944](#944)) ([495c6f0](495c6f0)) * **devdeps:** update dependency date-fns to v2.27.0 ([#967](#967)) ([fd32df3](fd32df3)) * **devdeps:** update dependency jest to v27.4.3 ([#969](#969)) ([7dc5dc7](7dc5dc7)) * **devdeps:** update dependency postcss to v8.4.4 ([#964](#964)) ([0a9ebb4](0a9ebb4)) * **devdeps:** update dependency prettier to v2.5.1 ([#968](#968)) ([fc30b77](fc30b77)) * **devdeps:** update storybook monorepo to v6.4.5 ([#965](#965)) ([8692741](8692741)) * **devdeps:** update storybook monorepo to v6.4.7 ([#966](#966)) ([bc0f17f](bc0f17f)) ### 🐛 Bug Fixes * **Touchable:** correct invalid css class ([#963](#963)) ([faac4c4](faac4c4))
|
🎉 This PR is included in version 0.126.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
8.3.11->8.4.4Release Notes
postcss/postcss
v8.4.4Compare Source
v8.4.3Compare Source
this.css.replace is not a functionerror.v8.4.2Compare Source
v8.4.1Compare Source
Stringifiertypes (by James Garbutt).v8.4.0Compare Source
PostCSS 8.4 brought ranges for warnings and errors, smaller
node_modulessize, lazy parsing to avoidPostCSS does nothingwarning, and TypeScript fixes.Thanks to Sponsors
This release was possible thanks to our community.
If your company wants to support the sustainability of front-end infrastructure or wants to give some love to PostCSS, you can join our supporters by:
Rages for Errors and Warnings
@adalinesimonian, the author of amazing Stylelint extension for VS Code, added ranges to errors and warnings.
It will improve DX in the IDE extension.
Lazy Parsing
Previously, we found that many tools run PostCSS even if the developer didn’t pass any PostCSS plugins. Parsing is the most expensive step in CSS processing. It led to a waste of resources without any reason.
We tried to resolve the problem by adding a
PostCSS does nothingwarning. But it didn’t force tool authors to be more careful with user’s resources.If PostCSS sees that tool call it without passing plugins (or changing parser/stringifier), PostCSS will not parse CSS (until toll will call
Result#root). In 8.4, @bogdan0083 (with the help of @WilhelmYakunin) tries to solve the problem in another way. It allows us to save resources and remove thePostCSS does nothingwarning.Install Size Reduction
With ≈60M weekly downloads, PostCSS has responsibility for the world’s resource spending.
Together with @7rulnik we reduced
source-map-jssize. It is transitive dependency of PostCSS.In 8.4, we moved to a fixed version of
source-map-js, which reduced thepostcsssize in yournode_modulesfrom ≈1 MB to 0.3 MB. With the huge popularity of PostCSS, it will free a lot of resources on our CIs.@kimoofey refactored all tests from the popular Jest framework to small and fast
uvu.It will not affect end-users. However, it reduced our
node_modulessize by 33 MB and made tests twice faster (yarn install & yarn unit: 24 → 13 seconds).TypeScript Fixes
Processortypes.Stringifiertypes (by @43081j).RootandDocumentin result values (by @43081j).Node#walkRules()types (by @hudochenkov).Other Changes
Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.