Open greenkeeper[bot] opened 7 years ago
Update to this version instead π
Update to this version instead π
Update to this version instead π
;;
after rules.Update to this version instead π
package.json
for node_modules
compiling cases.Update to this version instead π
end
position in at-rule without semicolon (by @hzlmn).Update to this version instead π
Update to this version instead π
Update to this version instead π
!IMPORTANT
support.Update to this version instead π
*
hack to declaration indent.Update to this version instead π
node_modules
(by @chriseppstein).source-map
0.6.Update to this version instead π
Update to this version instead π
Update to this version instead π
null
as input CSS.Update to this version instead π
Update to this version instead π
Node#prev
and Node#next
on missed parent.Update to this version instead π
Update to this version instead π
PostCSS 7.0 dropped Node.js 4 support and brought small features.
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:
last 2 version
not dead
not Explorer 11
not ExplorerMobile 11
@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:
TypeError: Cannot read property '0' of undefined
at /home/ai/Dev/test/app.css:10:4
at plugin (plugin.js:2:4)
at runPostCSS (runner.js:2:1)
@igorkamyshev added finally
method to LazyResult
to make it compatible with the latest Promise API.
Update to this version instead π
Update to this version instead π
dependency
postcss was updated from 5.2.18
to 7.0.3
.Update to this version instead π
dependency
postcss was updated from 5.2.18
to 7.0.4
.Update to this version instead π
dependency
postcss was updated from 5.2.18
to 7.0.5
.Update to this version instead π
dependency
postcss was updated from 5.2.18
to 7.0.6
.Update to this version instead π
dependency
postcss was updated from 5.2.18
to 7.0.7
.Update to this version instead π
Error
in CssSyntaxError
.dependency
postcss was updated from 5.2.18
to 7.0.8
.Update to this version instead π
support-colors
6.0.dependency
postcss was updated from 5.2.18
to 7.0.9
.Update to this version instead π
dependency
postcss was updated from 5.2.18
to 7.0.11
.Update to this version instead π
dependency
postcss was updated from 5.2.18
to 7.0.12
.Update to this version instead π
dependency
postcss was updated from 5.2.18
to 7.0.13
.Update to this version instead π
dependency
postcss was updated from 5.2.18
to 7.0.14
.Update to this version instead π
postcss-less
(by @mattlyons0)dependency
postcss was updated from 5.2.18
to 7.0.15
.Update to this version instead π
dependency
postcss was updated from 5.2.18
to 7.0.16
.dependency
postcss was updated from 5.2.18
to 7.0.17
.dependency
postcss was updated from 5.2.18
to 7.0.18
.dependency
postcss was updated from 5.2.18
to 7.0.19
.dependency
postcss was updated from 5.2.18
to 7.0.20
.dependency
postcss was updated from 5.2.18
to 7.0.21
.dependency
postcss was updated from 5.2.18
to 7.0.22
.dependency
postcss was updated from 5.2.18
to 7.0.23
.dependency
postcss was updated from 5.2.18
to 7.0.24
.dependency
postcss was updated from 5.2.18
to 7.0.25
.dependency
postcss was updated from 5.2.18
to 7.0.27
.dependency
postcss was updated from 5.2.18
to 7.0.28
.dependency
postcss was updated from 5.2.18
to 7.0.29
.
Version 6.0.0 of postcss just got published.
The version 6.0.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of postcss. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Release Notes
6.0 βMarquis OriasβPostCSS 6.0 dropped Node.js 0.12 support, cleaned
raws
API, added@apply
support 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 to 4.0 or 7.0 versions.
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:So, right now there are no needs to
moveTo
,moveAfter
andmoveBefore
methods. Regular insert methods have move behavior. In this case, we deprecated move methods.Also
Node#clone
now return the exactly copy of the node. In 6.0 it stops to cleanraws
.Every PostCSS plugin has
plugin.process
shortcut. 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 semicolon after mixin definition. In PostCSS 6.0 parser we covered this case, and node rules have
Rule#raws.ownSemicolon
for own semicolon.Stream Parser
In PostCSS 5.0 tokenizing and parsing were separated steps. As a result, we put all tokens to memory between steps. It works well in most of the cases. But memory usage was pretty big when you try to parse 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 latest tokens in memory. So 6.0 will use less memory.
Package Size
We care about
node_modules
size problem. So in 6.0 @lahmatiy and @h0tc0d3 removedjs-base64
dependency 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-env
islast 1 version
andnode 4
.Other Changes
:
in CSS.Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: