Repository - API - Source
image-set()
support (via
postcss-image-set-polyfill)
(#373 - @SuperOl3g)system-ui
keyword to define current System font-size (via
postcss-font-family-system-ui)
(#342 - @JLHwung)[data-thing=stuff i] {
to be
able to select all data-thing
attribute, without having to thing about the
case of the value) (#306 -
@Semigradsky)@apply
support (definitions limited to :root
selector)
(#291) - @pascalduez)overflow-wrap
fallback
(#280 - @MattDiMu)Oops!
"chalk" is undefined
.
(#266)rem
will now adjust its behavior according to browser option (IE 9
and IE 10 will only have px
in some places, where rem support is buggy, per
caniuse notes) (#264)postcss-cssnext/docs/content
rem
have
2 new parameters:rootValue
to define the root element font-size manuallyunitPrecision
for rounded values@nest
syntax. See postcss-nesting documentation.initial
value for all properties. Also it supports all: initial
.
Does not support all: unset
and all: inherit
. Plugin can be useful for
creating isolated components.all
specification: https://drafts.csswg.org/css-cascade/#all-shorthandall
browsers support: http://caniuse.com/#feat=css-allinitial
value specification:
https://drafts.csswg.org/css-cascade/#initial-valueinitial
value browser support: http://caniuse.com/#feat=css-initial-valuepre 2.0.0 information was related to cssnext
package.
compress
option now works again correctly. A recent update in cssnano
has introduced some minor breaking changes the way cssnext changed plugins
metadata (pluginName
). A direct minor change is that messages
(in console
or in css output) now show real origin (postcss plugin name) instead of a
vague "cssnext" origin.
(#195)url
option (postcss-url) have been updated in order to benefit from
severals fixes.@import
(#123)postcss-log-warnings
(deprecated) by
postcss-reporter
(#162)to
option automatically
(#159) If you were happy
with the previous CLI behavior (which was not rebasing url), you should
probably just add the --no-url
to keep the CSS as it was.compress
option now use cssnano v2.x
(#166)mkdirp
)
(#146)〉
to ›
@custom-selector :--{name}
syntax instead of
@custom-selector --{name}
The support of syntax without : and the warning
message will be remove in the next major release
(#97)plugins
option that allows you to pipe your own transformations
(#118)messages
option that allows you to see messages of transformations
(#88):any-link
pseudo class supportcompress
option use cssnano
instead of CSSWring.:matches()
selector pseudo class:not()
selector pseudo class level 4 (transpiled to
level 3)--watch
doesn't make some duplicate rebuild anymore.--watch
CLI option now checks for changes in imported files--config
CLI option--browsers
CLI optionimport
is not considered as a feature
anymore, but is now
directly an option for the API. It is still enabled by default.Before
cssnext({
features: {
import: {
root: "./src"
}
}
});
After
cssnext({
import: {
root: "./src"
}
});
url
option: non absolute url() are now rebased according to from
(and to
options if provided). Enabled by default.compress
option now accept CSSWring options directly.browsers
option can enable or disable features and is propagated to
autoprefixerrem
unitNode 4+ is supported.
All postcss plugins dependencies have been updated to latest version to ensure full PostCSS 6 compatibility.
Some breaking (minor) changes:
You can expect some other since all postcss plugins used have been updated to latest versions. If you have unexpected regression, please check corresponding plugins changelog before opening an issue.
@apply
This feature won't be included in next the major release of postcss-cssnext.
This most likely won't get any more support from browser vendors as the spec is yet considered deprecated and alternative solutions are being discussed. Read more about the reason here https://github.com/pascalduez/postcss-apply
Cannot find module 'exit'
error when an error came out
(#54)precision
& preserve
) & some
useless minor updatesdist/cssnext.js
){inline: true, sourceContent: true}
options
mutations
(gulp-cssnext#1)Before
var output = cssnext(input, {
features: {
// providing `true` (or omitting this value) instead of the following object
// was the default behavior
color: {
color: true
hexAlpha: true
hwb: true
rebeccapurple: true
}
}
})
Now
var output = cssnext(input, {
// as usual if you where using all features, you can just omit this values
features: {
colorFunction: true,
colorHexAlpha: true,
colorHwb: true,
colorRebeccapurple: true
}
}
})
features
propertiesBefore
//eg: preserve custom properties
var output = cssnext(input, {
preserve: true
});
Now
//eg: preserve custom properties
var output = cssnext(input, {
features: {
customProperties: {
preserve: true
}
}
});
map
option
(direct postcss option). Using this option make sourcemap
one to be ignored
and change the return value of cssnext()
(object instead of string)This change have been made to avoid collision between options (of each features).
bin
in npm files...bin
in package.json
for npmfrom
option doesn't enable sourcemap
automatically anymore✨ First release