Bump postcss from 8.3.11 to 8.4.1
Bumps postcss from 8.3.11 to 8.4.1.
Release notes
Sourced from postcss's releases.
8.4.1
- Fixed
Stringifier
types (by@43081j
).8.4 “President Camio”
PostCSS 8.4 brought ranges for warnings and errors, smaller
node_modules
size, lazy parsing to avoidPostCSS does nothing
warning, 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:
- Tidelift with a Spotify-like subscription model supporting all projects from your lock file.
- Direct donations in PostCSS & Autoprefixer Open Collective.
Rages for Errors and Warnings
@adalinesimonian
, the author of amazing Stylelint extension for VS Code, added ranges to errors and warnings.result.warn(msg, { index }) // One character warning at index result.warn(msg, { endIndex }) // Starts at node start, ends at endIndex result.warn(msg, { index, endIndex }) // Starts at index, ends at endIndex result.warn(msg, { start }) // Starts at start, ends at node end result.warn(msg, { end }) // Starts at node start, ends at end result.warn(msg, { start, end }) // Starts at start, ends at end result.warn(msg, { word }) // Starts at word location, ends at word index + length
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 nothing
warning. 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 nothing
warning.</tr></table>
... (truncated)
Changelog
Sourced from postcss's changelog.
8.4.1
- Fixed
Stringifier
types (by James Garbutt).8.4 “President Camio”
- Added ranges for errors and warnings (by Adaline Valentina Simonian).
- Added
Stringifier
types (by James Garbutt).- Added
Processor
types.- Removed
PostCSS does nothing
warning by lazy parser (Bogdan Dolin).- Fixed
Node#walkRules()
types (by Aleks Hudochenkov).- Fixed types
Root
andDocument
in result values (by James Garbutt).- Reduced npm install size by 0.5 MB.
- Moved tests from Jest to
uvu
(by Andrey Kim).- Fixed docs (by Paul Shryock).
Commits
-
5134979
Release 8.4.1 version -
1c7960d
Merge pull request #1681 from 43081j/default-stringifier -
47b5d62
fix: export stringifier as a default -
e72bf87
Release 8.4 version -
eef4041
Remove old plugin -
698556b
Show both VS Code plugins -
c9159ce
Merge pull request #1679 from hasnath1/patch-1 -
a054776
Update dependencies -
2b8ce5d
Merge pull request #1680 from TheDutchCoder/add-postcss-rem-to-px-plugin -
71f41fb
docs:📝 Add plugin to docs - Additional commits viewable in compare view