Open greenkeeper[bot] opened 7 years ago
Merging #79 into master will decrease coverage by
0.49%
. The diff coverage isn/a
.
@@ Coverage Diff @@
## master #79 +/- ##
=========================================
- Coverage 12.8% 12.31% -0.5%
=========================================
Files 40 40
Lines 1015 1015
=========================================
- Hits 130 125 -5
- Misses 885 890 +5
Impacted Files | Coverage Δ | |
---|---|---|
src/commands/index.js | 75.75% <0%> (-15.16%) |
:arrow_down: |
Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact)
,ø = not affected
,? = missing data
Powered by Codecov. Last update fe5bfde...8b9ff27. Read the comment docs.
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.Update to this version instead 🚀
::placeholder
prefix for Edge.inherit
/initial
/unset
values for flex-direction
.Update to this version instead 🚀
browserslist
option instead of browsers
.Invalid array length
error during indent changes.Update to this version instead 🚀
Autoprefixer 7.2 brings better Grid support for IE
and autoprefixer-info
CLI tool.
With grid: true
option Autoprefixer adds -ms-
prefixes to Grid Layout properties. But this feature was very limited.
In 7.0 we dramatically improved Grid support for IE. @Alex7Kom added grid-area
and improved grid-row
and grid-column
support. @evgeny-petukhov added grid-template-areas
and grid-template
support.
Even this complex emoji example will work with new Autoprefixer (output):
body {
display: grid;
grid-template-rows: auto 300px;
grid-template-columns: 3fr 1fr;
grid-template-areas: "🎩 🎩"
"🍔 📰"
"👞 👞";
}
header {
grid-area: 🎩;
}
nav {
grid-area: 🍔;
}
main {
grid-area: 📰;
}
footer {
grid-area: 👞;
}
Just don’t forget to set grid: true
option:
auoprefixer({ grid: true })
Autoprefixer 7.2 ships with new CLI tool to check which browsers are selected and which properties will be prefixed.
Just go to your project directory and run npx autoprefixer-info
:
Browsers:
Edge: 16
These browsers account for 0.04% of all users globally
At-Rules:
@viewport: ms
Selectors:
::placeholder: ms
Properties:
user-select: ms
hyphens: ms
appearance: webkit
scroll-snap-type: ms
scroll-snap-coordinate: ms
scroll-snap-destination: ms
scroll-snap-points-x: ms
scroll-snap-points-y: ms
flow-into: ms
flow-from: ms
region-fragment: ms
text-spacing: ms
Also, @pdokas added default value (current working dir) for from
option in autoprefixer.info()
.
radial-gradient
properties warning.reverse
animation direction.Update to this version instead 🚀
Update to this version instead 🚀
_autoprefixerDisabled is undefined
issue.Update to this version instead 🚀
grid-template-areas
in @media
(by @evgeny-petukhov).Update to this version instead 🚀
Fix IE 10 support
Update to this version instead 🚀
Update to this version instead 🚀
Autoprefixer 8.1 brings overscroll-behavior
and better Grid support.
@Malvoz suggested the great idea to polyfill overscroll-behavior
for IE 11 and Edge by -ms-scroll-chaining
.
.none {
-ms-scroll-chaining: none;
overscroll-behavior: none;
}
.contain {
-ms-scroll-chaining: none;
overscroll-behavior: contain;
}
.auto {
-ms-scroll-chaining: chained;
overscroll-behavior: auto;
}
Note, that overscroll-behavior-x
and overscroll-behavior-y
are not supported since -ms-
property doesn’t have this freedom.
@evgeny-petukhov continues his amazing work and now Autoprefixer polyfills Grid Layout for IE in more cases.
He added grid-template
shortcut support and improve support of grid-column-end
and grid-row-end
.
Grid properties were fixed in @supports
. We recommend:
@supports (display: grid)
.@supports (grid-gap: 0)
.Note, that you need grid: true
option to Autoprefixer to add -ms-
prefixes for Grid Layout.
Update to this version instead 🚀
Autoprefixer 8.2 brings color-adjust
support.
@YozhikM, @soul-wish, and @yuriyalekseyev did a great work. They added new data to Can I Use and implemented a new feature to Autoprefixer.
body {
-webkit-print-color-adjust: exact;
color-adjust: exact;
}
Update to this version instead 🚀
Autoprefixer 8.3 adds @media
support for grid-template
and fixes gradient direction warning.
@evgeny-petukhov continues his great work for Grid Layout support in Autoprefixer.
Now he improved @media
support. Now this CSS will work in IE:
body {
grid-template:
[header-left] "head head" 30px [header-right]
[main-left] "nav main" 1fr [main-right]
[footer-left] "nav foot" 30px [footer-right]
/ 120px repeat(4, 250px 10px);
}
header {
grid-area: head;
}
main {
grid-area: main;
}
footer {
grid-area: footer;
}
@media (min-width: 1000px) {
body {
grid-template:
[header-left] "head" 30px [header-right]
[main-left] "main" 1fr [main-right]
[footer-left] "footer" 30px [footer-right]
/ 1fr;
}
}
Don’t forget that Autoprefixer inserts Grid Layout prefixes only if you set grid: true
option.
@radium-v found that Autoprefixer show warning even if cover
is outside of radial-gradient
.
a {
background: radial-gradient(#fff, transparent) 0 0 / cover no-repeat #f0f;
}
@kotfire improve old direction detection and fix this issue.
Update to this version instead 🚀
Autoprefixer 8.4 brings new control comment to ignore next line.
@vostrik implemented the @levin-du’s idea of having control comment to disable only next property/rule:
.logo {
/* autoprefixer: ignore next */
user-select: none; /* ← ignored */
mask: url(mask.jpg); /* ← will be prefixed */
}
/* autoprefixer: ignore next */
::placholder /* ← ignored */ {
text-decoration-style: dotted; /* ← will be prefixed */
}
Update to this version instead 🚀
Update to this version instead 🚀
Autoprefixer 8.5 brings grid-gap
support and fix radial-gradient
.
@evgeny-petukhov continues his amazing work of adding CSS Grid Layout support to Autoprefixer.
Now he brought grid-gap
. It is amazing work since IE 11 has gaps support in -ms-
grids.
To add grid-gap
support for IE 11 Autoprefixer adds addition grid cells. Unfortunately, it will work only if you have grid-template
in the same rule with grid-gap
. We had a big discussion with a community about these limits.
.a-shortcut {
grid-gap: 33px;
-ms-grid-rows: 1fr 33px minmax(100px, 1fr) 33px 2fr;
-ms-grid-columns: 1fr 33px 100px 33px 1fr;
grid-template:
"head head head" 1fr
"nav main main" minmax(100px, 1fr)
"nav foot foot" 2fr /
1fr 100px 1fr;
}
Old gradients with prefixes used a different direction syntax. Autoprefixer converts direction to old syntax (or warn you to rewrite direction from old to new syntax).
But it has an issue with extent keywords like circle closest-corner
. @BaliBalo reported it and 8.5 fixed it:
.mask {
-webkit-mask-image: -webkit-radial-gradient(100% 50%, circle closest-corner, black, white);
mask-image: radial-gradient(circle closest-corner at 100% 50%, black, white);
}
Update to this version instead 🚀
-webkit-fill-available
.Update to this version instead 🚀
Autoprefixer 8.6 brings gap
property support and two values support for grid-gap
/gap
.
CSSWG renamed grid-gap
property to gap
.
@yepninja added gap
support with 2 values support.
Grid layout code bellow will work even in IE if you pass grid: true
option to Autoprefixer:
.main {
gap: 10px 20px;
grid-template-columns: 1fr 1fr 1fr;
grid-template-areas: "head head head"
"nav main main"
"nav foot foot";
}
ignoreUnknownVersions
option for BrowserslistUpdate to this version instead 🚀
grid-template
with media queries (by @yepninja)Update to this version instead 🚀
@media
(by @yepninja).Update to this version instead 🚀
grid
option for grid properties in autoprefixer --info
.Update to this version instead 🚀
stretch
prefix in Chrome >= 46.Update to this version instead 🚀
Update to this version instead 🚀
Autoprefixer 9.0 brings Browserslist 4.0 and drops Node.js 4 support.
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 targets:
last 2 version
not dead
not Explorer 11
not ExplorerMobile 11
node 10
node 8
node 6
Autoprefixer Rails 9.0 dropped the RubyRacer and Sprockets 3 support.
Autoprefixer 9.0 uses Browserslist 4.0 to get your target browsers.
Now you use Browserslist to specify Node.js versions. Babel 7 will use Browserslist config as well.
Also, Browserslist 4.0 will warn you if you didn’t update Can I Use DB for last than 6 month.
Autoprefixer 9.0 uses PostCSS 7.0
Update to this version instead 🚀
Update to this version instead 🚀
Update to this version instead 🚀
Autoprefixer 9.1 brings background-clip: text
and fix span
in IE Grid.
background-clip: text
beome to be the standard and got Edge support. So we added it to Autoprefixer:
.title {
background: linear-gradient(yellow, red);
-webkit-background-clip: text;
background-clip: text;
}
Note, that Edge expect -webkit-
prefix for this property.
@bogdan0083 fixed an issue when media-query override some grid-template
.
Update to this version instead 🚀
grid-gap
through @media
(by @bogdan0083).grid-template
and @media
(by @bogdan0083).span X
Grid prefix (by @@bogdan0083).Update to this version instead 🚀
autoprefixer --info
in new Node.js.Update to this version instead 🚀
@babel/register
from dependencies.dependency
autoprefixer was updated from 6.7.7
to 9.2.0
.dependency
autoprefixer was updated from 6.7.7
to 9.2.1
.Update to this version instead 🚀
dependency
autoprefixer was updated from 6.7.7
to 9.3.0
.Update to this version instead 🚀
Autoprefixer 9.3 brings place-self
support for Grid Layout
place-self
@Dan503 and @bogdan0083 found a way to impement support for another Grid property
.grid > .center {
place-self: center;
}
.grid > .center {
-ms-grid-row-align: center;
-ms-grid-column-align: center;
place-self: center;
}
@Dan503 and @bogdan0083 also detect and fixed issue with Grid row/column span inheritance.
dependency
autoprefixer was updated from 6.7.7
to 9.3.1
.Update to this version instead 🚀
repeat()
value (by @bogdan0083).dependency
autoprefixer was updated from 6.7.7
to 9.4.0
.Update to this version instead 🚀
Autoprefixer 9.4.0 brings limited autoplacement support to the IE CSS Grid.
If the grid
option is set to "autoplace"
, limited autoplacement support is now added to the Autoprefixer CSS Grid translations. You can also use the /* autoprefixer grid: autoplace */
control comment to enable autoplacement directly in your CSS.
In order to use the new autoplacement feature, you must define both rows and columns when declaring the grid template.
/* Input CSS */
/* autoprefixer grid: autoplace */
.autoplacement-example {
display: grid;
grid-template-columns: 1fr 1fr;
grid-template-rows: auto auto;
grid-gap: 20px;
}
/* Output CSS */
/* autoprefixer grid: autoplace */
.autoplacement-example {
display: -ms-grid;
display: grid;
-ms-grid-columns: 1fr 20px 1fr;
grid-template-columns: 1fr 1fr;
-ms-grid-rows: auto 20px auto;
grid-template-rows: auto auto;
grid-gap: 20px;
}
.autoplacement-example > *:nth-child(1) {
-ms-grid-row: 1;
-ms-grid-column: 1;
}
.autoplacement-example > *:nth-child(2) {
-ms-grid-row: 1;
-ms-grid-column: 3;
}
.autoplacement-example > *:nth-child(3) {
-ms-grid-row: 3;
-ms-grid-column: 1;
}
.autoplacement-example > *:nth-child(4) {
-ms-grid-row: 3;
-ms-grid-column: 3;
}
Autoplacement support in Autoprefixer is currently very limited in what it can do. Please read the Grid Autoplacement support in IE section before using this new feature.
Thanks to @bogdan0083 for implementing the new feature, @Dan503 for documenting it, and @evandiamond for coming up with the initial idea.
dependency
autoprefixer was updated from 6.7.7
to 9.4.1
.dependency
autoprefixer was updated from 6.7.7
to 9.4.2
.Update to this version instead 🚀
dependency
autoprefixer was updated from 6.7.7
to 9.4.3
.dependency
autoprefixer was updated from 6.7.7
to 9.4.4
.dependency
autoprefixer was updated from 6.7.7
to 9.4.5
.Update to this version instead 🚀
text-decoration-skip-ink
support.dependency
autoprefixer was updated from 6.7.7
to 9.4.6
.Update to this version instead 🚀
dependency
autoprefixer was updated from 6.7.7
to 9.4.7
.Update to this version instead 🚀
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: