chore(deps): update dependency postcss to v7#177
Open
dev-mend-for-github-com[bot] wants to merge 1 commit intoelectron-upgradefrom
Open
chore(deps): update dependency postcss to v7#177dev-mend-for-github-com[bot] wants to merge 1 commit intoelectron-upgradefrom
dev-mend-for-github-com[bot] wants to merge 1 commit intoelectron-upgradefrom
Conversation
Author
|
This file contains hidden or 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
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:
5.2.4→7.0.36By merging this PR, the issue #6 will be automatically resolved and closed:
Release Notes
postcss/postcss (postcss)
v7.0.36Compare Source
v7.0.35Compare Source
v7.0.34Compare Source
postcss-scss2.v7.0.33Compare Source
v7.0.32Compare Source
v7.0.31Compare Source
v7.0.30Compare Source
v7.0.29Compare Source
Processor#version.v7.0.28Compare Source
v7.0.27Compare Source
v7.0.26Compare Source
v7.0.25Compare Source
v7.0.24Compare Source
v7.0.23Compare Source
Processor#version.v7.0.22Compare Source
npm fund.v7.0.21Compare Source
nodesproperty to node constructor.v7.0.20Compare Source
nodesproperty to node constructor.v7.0.19Compare Source
nodesproperty to node constructor.v7.0.18Compare Source
v7.0.17Compare Source
v7.0.16Compare Source
v7.0.15Compare Source
v7.0.14Compare Source
postcss-less(by Matt Lyons).v7.0.13Compare Source
v7.0.12Compare Source
v7.0.11Compare Source
v7.0.10Compare Source
v7.0.9Compare Source
v7.0.8Compare Source
support-colors6.0.v7.0.7Compare Source
ErrorinCssSyntaxError.v7.0.6Compare Source
v7.0.5Compare Source
v7.0.4Compare Source
v7.0.3Compare Source
Processor#version.v7.0.2Compare Source
Processor#version.v7.0.1Compare Source
nodesproperty to node constructor.v7.0.0: 7.0 “President Amy”Compare Source
PostCSS 7.0 dropped Node.js 4 support and brought small features.
Breaking Changes
We removed Node.js 4 and Node.js 9 support since it doesn’t have security updates anymore.
We removed IE and “dead” browsers (without security updates) from Babel’s Browserslist. Don't worry, PostCSS still generate IE-compatible code. These changes affect websites which run PostCSS on client-side like CodePen.
New Features
@nikhilgaba added cute thing for plugin developers. If an error was happened in
Container#walk()circle, PostCSS will show in stack trace CSS node, which causes this error:@igorkamyshev added
finallymethod toLazyResultto make it compatible with the latest Promise API.Other Changes
v6.0.23Compare Source
v6.0.22Compare Source
Node#prevandNode#nexton missed parent.v6.0.21Compare Source
yarnpkg.comissue.v6.0.20Compare Source
nullas input CSS.v6.0.19Compare Source
sourcefield in TypeScript definitions (by Sylvain Pollet-Villard).v6.0.18Compare Source
v6.0.17Compare Source
v6.0.16Compare Source
v6.0.15Compare Source
fromoption onprocess().then()call.v6.0.14Compare Source
v6.0.13Compare Source
in
node_modules(by Chris Eppstein).source-map0.6.v6.0.12Compare Source
*hack to declaration indent.v6.0.11Compare Source
!IMPORTANTsupport.v6.0.10Compare Source
v6.0.9Compare Source
v6.0.8Compare Source
v6.0.7Compare Source
v6.0.6Compare Source
endposition in at-rule without semicolon (by Oleh Kuchuk).v6.0.5Compare Source
package.jsonfornode_modulescompiling cases.v6.0.4Compare Source
;;after rules.v6.0.3Compare Source
v6.0.2Compare Source
v6.0.1Compare Source
sourcefield in TypeScript definitions (by Sylvain Pollet-Villard).v6.0.0: 6.0 “Marquis Orias”PostCSS 6.0 drops support for Node.js 0.12, cleans the
rawsAPI, adds support for@apply, and uses less memory.Breaking Changes
Node.js stopped 0.12 support in January 01. So PostCSS dropped Node.js 0.12 from all tests. Please update your Node.js version to 4.0 or 7.0.
In 6.0 we fixed our mistakes in API design. First, if node already had a parent, insert methods (
append,insertAfter, etc) will not clone it anymore. In 6.0 inserts methods will remove inserted node from previous parent:Now,
moveTo,moveAfter&moveBeforeare deprecated because regular insert methods have this move behavior.Also
Node#clonenow returns the exact copy of a node. In 6.0 it no longer cleansraws.Every PostCSS plugin has
plugin.processshortcut. In 6.0 we split process and plugin options in this shortcut:In the new major release, we finally remove all deprecated methods from PostCSS 4.0. It should not be a big problem because we show deprecated warnings for them for 2 years. Most of the plugins updated their API.
New Methods and Properties
Since we removed deprecated methods from PostCSS 4.0, in 6.0 we were free to add
before()andafter()shortcuts, similar to DOM API methods.Chrome 51 started to support “native CSS mixins” from @tabatkins spec under the flag:
PostCSS 5.0 could parse it pretty well, but in some cases, it lost the semicolon after a mixin definition. In PostCSS 6.0 parser we covered this case, and node rules have
Rule#raws.ownSemicolonfor their own semicolon.Stream Parser
In PostCSS 5.0 tokenizing and parsing were separated steps. As a result, we wrote all tokens into memory between steps. It worked well most of the time, but had a large memory usage when parsing really big CSS files (more than 25 MB).
In 6.0 @hzlmn rewrote parser, and now parser and tokenizer work together (stream parser). As a result, we put only a few of the latest tokens in memory. So 6.0 will use less memory.
Package Size
We care about
node_modulessize problem. So in 6.0 @lahmatiy and @h0tc0d3 removedjs-base64dependency to use native Node.js and Browsers ways to base64 encoding.Also, PostCSS was moved to
babel-preset-env. Instead of regularbabel, it will compile only necessary parts of ES6. So build in npm packages will be cleaner. Current browserslist config forbabel-preset-envislast 1 versionandnode 4.Other Changes
:in CSS.v5.2.18in
node_modules(by Chris Eppstein).v5.2.17Compare Source
postcss-sasssuggestion to syntax error on.sassinput.v5.2.16Compare Source
v5.2.15Compare Source
v5.2.14Compare Source
v5.2.13Compare Source
v5.2.12Compare Source
v5.2.11Compare Source
v5.2.10Compare Source
v5.2.9Compare Source
v5.2.8Compare Source
v5.2.7Compare Source
v5.2.6Compare Source
postcss.vendorfor values with spaces (by 刘祺).v5.2.5Compare Source