-
Notifications
You must be signed in to change notification settings - Fork 0
chore(deps): update dependency postcss to v8.5.6 #11
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
Conversation
|
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/keith-cy/keith-cy/BzSC6Edz2ZxPiZH6obUzYE8VXD9d |
6addef2 to
d05edc4
Compare
d05edc4 to
3e817bc
Compare
3e817bc to
9f41eea
Compare
9f41eea to
fbbfa71
Compare
fbbfa71 to
ca93898
Compare
ca93898 to
da7c377
Compare
da7c377 to
0dc8e04
Compare
0dc8e04 to
ced6928
Compare
ced6928 to
a7cda6f
Compare
5040f55 to
3297f0d
Compare
3297f0d to
5f04c96
Compare
5f04c96 to
870274f
Compare
870274f to
1eae86a
Compare
1eae86a to
ea13762
Compare
ea13762 to
0628b96
Compare
0628b96 to
88b063a
Compare
88b063a to
503f12d
Compare
Renovate Ignore NotificationBecause you closed this PR without merging, Renovate will ignore this update ( If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. |
This PR contains the following updates:
8.2.6→8.5.6Release Notes
postcss/postcss (postcss)
v8.5.6Compare Source
ContainerWithChildrentype discriminating (by @Goodwine).v8.5.5Compare Source
package.json→exportscompatibility with some tools (by @JounQin).v8.5.4Compare Source
v8.5.3Compare Source
Unknown worderror (by @hiepxanh).v8.5.2Compare Source
v8.5.1Compare Source
v8.5.0: 8.5 “Duke Alloces”Compare Source
PostCSS 8.5 brought API to work better with non-CSS sources like HTML, Vue.js/Svelte sources or CSS-in-JS.
@romainmenke during his work on Stylelint added
Input#documentin additional toInput#css.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:
v8.4.49Compare Source
source.offset(by @romainmenke).v8.4.48Compare Source
v8.4.47Compare Source
v8.4.46Compare Source
Cannot read properties of undefined (reading 'before').v8.4.45Compare Source
v8.4.44Compare Source
markClean is not a functionerror.v8.4.43Compare Source
markClean is not a functionerror.v8.4.42Compare Source
v8.4.41Compare Source
v8.4.40Compare Source
v8.4.39Compare Source
CssSyntaxErrortypes (by @romainmenke).v8.4.38Compare Source
endIndex: 0in errors and warnings (by @romainmenke).v8.4.37Compare Source
original.column are not numberserror in another case.v8.4.36Compare Source
original.column are not numberserror on broken previous source map.v8.4.35Compare Source
!innode.parent.nodestype.undefinedto node adding method to simplify types.v8.4.34Compare Source
AtRule#nodestype (by Tim Weißenfels).v8.4.33Compare Source
NoWorkResultbehavior difference with normal mode (by Romain Menke).NoWorkResultusage conditions (by @ahmdammarr).v8.4.32Compare Source
postcss().process()types (by Andrew Ferreira).v8.4.31Compare Source
\rparsing to fix CVE-2023-44270.v8.4.30Compare Source
v8.4.29Compare Source
Node#source.offset(by Ido Rosenthal).v8.4.28Compare Source
Root.source.endfor better source map (by Romain Menke).Result.roottypes whenprocess()has no parser.v8.4.27Compare Source
Containerclone methods types.v8.4.26Compare Source
v8.4.25Compare Source
v8.4.24Compare Source
Plugintypes.v8.4.23Compare Source
v8.4.22Compare Source
node16(by Remco Haszing).v8.4.21Compare Source
Input#errortypes (by Aleks Hudochenkov).v8.4.20Compare Source
@layer.v8.4.19Compare Source
v8.4.18Compare Source
absolute: truewith emptysourceContent(by Rene Haas).v8.4.17Compare Source
Node.before()unexpected behavior (by Romain Menke).v8.4.16Compare Source
RootAST migration.v8.4.15Compare Source
v8.4.14Compare Source
v8.4.13Compare Source
append()error after using.parent(by Jordan Pittman).v8.4.12Compare Source
package.fundingto have same value between all PostCSS packages.v8.4.11Compare Source
Declaration#raws.valuetype.v8.4.10Compare Source
package.fundingURL format.v8.4.9Compare Source
package.funding(by Álvaro Mondéjar).v8.4.8Compare Source
v8.4.7Compare Source
Node#warn()type (by Masafumi Koba).,.v8.4.6Compare Source
.rootaccess for plugin-less case.v8.4.5Compare Source
rawstypes to make object extendable (by James Garbutt).v8.4.4Compare Source
source.offset(by @romainmenke).v8.4.3Compare Source
CssSyntaxErrortypes (by @romainmenke).v8.4.2Compare Source
Node#source.offset(by Ido Rosenthal).v8.4.1Compare Source
v8.4.0: 8.4 “President Camio”Compare 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.Migration from Jest to
uvu@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
v8.3.11Compare Source
v8.3.10Compare Source
Maximum call stackissue of some source maps (by Yeting Li).v8.3.9Compare Source
nanocolorstopicocolors.v8.3.8Compare Source
nanocolors.v8.3.7Compare Source
colorettetonanocolors.package.json(by Christian Oliff).v8.3.6Compare Source
missed semicolonerror (by @Gusted).v8.3.5Compare Source
v8.3.4Compare Source
v8.3.3Compare Source
postcssdependency duplication in custom parsers.v8.3.2Compare Source
v8.3.1Compare Source
v8.3.0: 8.3 “Duke Murmur”Compare Source
PostCSS 8.3 improved source map parsing performance, added
Node#assign()shortcut, and experimentalDocumentnode to AST.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:
Source Map Performance
Because PostCSS needs synchronous API, we can’t move from the old `source-map 0.6 to 0.7 (many other open-source projects too).
@7rulnik forked
source-map0.6 tosource-map-jsand back-ported performance improvements from 0.7. In 8.3 we switched fromsource-mapto thissource-map-jsfork.You map see 4x performance improvements in parsing map from processing step before PostCSS (for instance, Sass).
DocumentNodesThanks to @gucong3000, PostCSS already parse CSS from HTML and JS files (CSS-in-JS templates and objects).
But his plugin need big updates. @hudochenkov from stylelint team decided to create new parsers for styles inside CSS-in-JS, HTML, and Markdown.
He suggested adding new
Documentnode type to PostCSS AST to keep multipleRootnodes inside and JS/HTML/Markdown code blocks between these style blocks.This is an experimental feature. Some aspects of this node could change within minor or patch version releases.
Node#assign()ShortcutThe creator of famous
postcss-preset-envand many other PostCSS tools, @jonathantneal suggested a nice shortcut to change multiple properties in the node:v8.2.15Compare Source
listtype definitions (by @n19htz).v8.2.14Compare Source
source-mapfrom client-side bundle (by Barak Igal).v8.2.13Compare Source
v8.2.12Compare Source
package.jsonexports.v8.2.11Compare Source
DEP0148warning in Node.js 16.v8.2.10Compare Source
v8.2.9Compare Source
NodeErrorOptionstype (by Rouven Weßling).v8.2.8Compare Source
v8.2.7Compare Source
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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 was generated by Mend Renovate. View the repository job log.