2.5.2

• Fixed: pleeease-filters has been udpated to v3, in order to provide a real
  PostCSS plugin
  (#274)

2.5.1

Oops!

• Fixed: "chalk" is undefined.
  (#266)
• Fixed: typo in related warning.

2.5.0

• Added: cssnext will now warn you when you have duplicates plugins.
  This is a really common mistake, people include plugins that are already
  included in cssnext and maybe sometimes in an inaccurate position.
  Most tutorial on the internet are wrong (probably 99%)
  and show provide duplicates in their examples.
  (eg: autoprefixer + cssnext - but cssnext already includes autoprefixer).
  In order to fix this, here is a warning. You are welcome.
  Read more about this issue
• Added: 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)

2.4.0

• Added: documentation is now included in the npm package in
  postcss-cssnext/docs/content

2.3.0

• Added: we use latest version of pixrem(@^3)
  (6d44410)
  So now rem have
  2 new parameters:
  • rootValue to define the root element font-size manually
  • unitPrecision for rounded values

2.2.0

• Added: postcss-nesting
  (b31f167).
  Supports nesting via the @nest syntax. See postcss-nesting documentation.

2.1.0

• Added: postcss-initial
  (a907881).
  Supports 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-shorthand
  • all browsers support: http://caniuse.com/#feat=css-all
  • initial value specification: https://drafts.csswg.org/css-cascade/#initial-value
  • initial value browser support: http://caniuse.com/#feat=css-initial-value

2.0.1

• Fixed: plugin can be consumed correctly from es5 environment
  (7d6d3c0).

2.0.0

• Added: support for PostCSS v5.x
• Removed: support for PostCSS v4.x
  (b5ece99...8907c13).

1.8.4

• Fixed: 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)