Closed greenkeeper[bot] closed 7 years ago
Update to this version instead 🚀
Update to this version instead 🚀
Autoprefixer 7.1 brings unicode-bidi
support, -webkit-appearance
to Edge and fix intrinsic widths prefixes in Grid Layout.
unicode-bidi
Autoprefixer 7.1 will add prefixes for isolate
, plaintext
and isolate-override
values in unicode-bidi
:
.foo {
unicode-bidi: -webkit-isolate;
unicode-bidi: isolate;
}
-webkit-appearance
Prefixes sometime could be very strange. Edge started to support appearance
property with a prefix. But because of many only-for-Safari websites it supports -webkit-appearance
instead of -ms-appearance
.
Autoprefixer 7.1 knows it and will generate -webkit-appearance
even if you set only "last 1 Edge version"
in browserslist config.
min-content
, stretch
and other Intrinsic sizes was fixed in grid-template-columns
and other Grid Layout properties.
.foo {
grid-template-columns: minmax(100px, -webkit-min-content);
grid-template-columns: minmax(100px, min-content);
}
info()
By accident Browserslist 1 loaded config from current working dir if file path was missed. In Browserslist 2 we fixed it and now you must specify path to file in explicit way.
It is not a problem for Autoprefixer user, because Autoprefixer takes CSS file path from PostCSS.
But autoprefixer.info()
stopped to load conifg in 7.0. In 7.1 we added from
option to info()
.
Set the path to your CSS file and info()
will show what prefixes and why it will added to this CSS file:
autoprefixer.info({ from: './scr/app.css' })
//=> Browsers:
// Chrome: 58
//
// These browsers account for 1.68% of all users globally
//
// Selectors:
// :fullscreen: webkit
// …
Update to this version instead 🚀
-webkit-
intrinsic prefixes in Grid Layout (by @yisibl).Update to this version instead 🚀
text-decoration
shortcut support.
Version 7.0.0 of autoprefixer just got published.
The version 7.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 autoprefixer. 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
7.0 “Coelestem adspicit lucem”Autoprefixer 7.0 uses PostCSS 6.0, Browserslist 2.0 and
caniuse-lite
.Browserslist 2.0
Browserslist 2.0 and
caniuse-lite
by @ben-eb are the main changes in Autoprefixer 7.0. We wrote an article about these changes:> Autoprefixer 7.0 and Browserslist 2.0
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.
IE has very basic support of Grid Layout. So Autoprefixer added
-ms-
prefixes and change property syntax. Unfortunately, IE supports a really small subset of Grid Layout. So prefixes were not really useful. This is why we disabled Grid Layout prefixes by default. But you still can enable it:Babel
Autoprefixer was one of the biggest CoffeeScript projects. We thought to rewrite it, but reasons were small, and work was big. But @Semigradsky used great decaffeinate tool for automatically CoffeeScript → ES6 converting, and now all Autoprefixer sources are written in JS.
PostCSS 6.0
New PostCSS uses stream parser and uses less memory. Also, it uses less space in
node_modules
.Other Changes
^
for Browserslist dependencies, instead of~
.-ms-grid-column-align
.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: