changelogs.md


moox/postcss-cssnext

Repository  -  API  -  Source

3.1.0

January 22, 2018
  • Update postcss-font-family-system-ui to version 3.0 by @JLHwung in #443
  • Update postcss-cli usage example in docs by @RyanZim in #444

3.0.2

July 10, 2017
  • Fixed: remove incorrect "postinstall" npm script (#404 - @MoOx)

3.0.1

July 10, 2017
  • Fixed: specify the actual require peer dependency for caniuse database (caniuse-lite is used since latest caniuse-api latest major bump) (@MoOx)
  • Fixed: bump dependencies not updated to PostCSS@6 (#401 - @MoOx)

3.0.0

July 5, 2017

2.11.0

May 15, 2017

2.10.0

March 16, 2017
  • Added: system-ui keyword to define current System font-size (via postcss-font-family-system-ui) (#342 - @JLHwung)
  • Added: new auto-deactivation rules in features map (#345 - @Semigradsky)

2.9.0

November 28, 2016

2.8.0

September 5, 2016
  • Added: attribute case insensitive support (eg: [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)

2.7.0

June 28, 2016
  • Added: @apply support (definitions limited to :root selector) (#291) - @pascalduez)

2.6.0

June 1, 2016
  • Added: overflow-wrap fallback (#280 - @MattDiMu)

2.5.2

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

2.5.1

March 14, 2016

Oops!

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

2.5.0

March 14, 2016
  • 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

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

2.3.0

December 16, 2015
  • 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

October 21, 2015

2.1.0

September 16, 2015

2.0.1

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

2.0.0

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

pre 2.0.0 information was related to cssnext package.

1.8.4

August 24, 2015
  • 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)

1.8.3

August 6, 2015
  • Fixed: url option (postcss-url) have been updated in order to benefit from severals fixes.

1.8.2

July 23, 2015
  • Fixed: CLI watcher now works watchs correctl multiples @import (#123)

1.8.1

July 15, 2015
  • Added: cssnext now throw an error if used as a webpack loader to prevent unexpected usage with a recommendation for cssnext-loader (#61)

1.8.0

June 29, 2015
  • Fixed: replacement of postcss-log-warnings (deprecated) by postcss-reporter (#162)
  • Fixed: CLI now add 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.
  • Changed: compress option now use cssnano v2.x (#166)
  • Added: CLI output file dirname is now automatically created (using mkdirp) (#146)

1.7.1

June 19, 2015
  • Fixed: bullet for browser messages should be visible on Chrome Windows. Changed from to

1.7.0

June 17, 2015
  • Added: warning to deprecate previous (wrong) custom selectors syntax. Previously they were working with and without pseudo syntax ':' which is incorrect according to specs Now you must use @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)
  • Added: plugins option that allows you to pipe your own transformations (#118)
  • Added: messages option that allows you to see messages of transformations (#88)
  • Added: :any-link pseudo class support

1.6.0

June 2, 2015
  • Added: prevent mutability issues with frozen options objects (#147)

1.5.2

May 27, 2015
  • Fixed: support for autoprefixer 5.2 (#131)

1.5.1

May 25, 2015
  • Fixed: when printing a bug report in CLI, url was not printed, due to a replacement of colors lib by chalk in 1.5.0 (#129)

1.5.0

May 23, 2015
  • Changed: compress option use cssnano instead of CSSWring.

1.4.0

May 1, 2015
  • Added: support for :matches() selector pseudo class
  • Added: support for :not() selector pseudo class level 4 (transpiled to level 3)

1.3.1

May 1, 2015
  • Fixed: CLI --watch doesn't make some duplicate rebuild anymore.

1.3.0

April 15, 2015
  • Added: hexadecimal fallback for rgba() color

1.2.3

April 10, 2015
  • Fixed: --watch doesn't output console.log() related to watcherd/unwatched files anymore

1.2.2

April 9, 2015
  • Changed: upgrade chokidar to stable 1.0.0 (used for cssnext --watch)

1.2.1

March 2, 2015
  • Fixed: remove some deprecation notice related to postcss 4.1 (postcss#272)

1.2.0

April 2, 2015
  • Added: pseudoElements single colon fallback for pseudoElements double colons
  • Added: --watch CLI option now checks for changes in imported files

1.1.0

March 5, 2015
  • Added: --config CLI option
  • Added: --browsersCLI option

1.0.1

February 18, 2015
  • Fixed: cssnext binary doesn't exit on an error if --watch is enabled (#69)

1.0.0

February 6, 2015
  • Changed: upgraded to postcss v4.x
  • Changed: import 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"
  }
});
  • Added: url option: non absolute url() are now rebased according to from (and to options if provided). Enabled by default.
  • Added: compress option now accept CSSWring options directly.
  • Added: browsers option can enable or disable features and is propagated to autoprefixer
  • Added: px fallback for rem unit

0.12.0

Node 4+ is supported.

Changed: upgrade to PostCSS 6

All postcss plugins dependencies have been updated to latest version to ensure full PostCSS 6 compatibility.

Some breaking (minor) changes:

  • image-set polyfill change 2x from 144dpi to 192dpi
  • whitespace changes for image-set polyfill output
  • rebeccapurpule is now an hexa number
  • custom-selector does not output useless (empty) blocks with a selector with no rules associated

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.

Added: warning is emitted is you use custom property sets and @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

0.6.6

December 22, 2014
  • Fixed: Cannot find module 'exit' error when an error came out (#54)

0.6.5

December 16, 2014

0.6.4

December 11, 2014
  • Changed: upgrade postcss-import to 4.0.0 for windows compatibility
  • Added: Windows compatibility (by building test on AppVeyor)

0.6.3

December 9, 2014
  • Changed: upgrade to csswring v2.0.0 (postcss 3 ready). This is removing the boring warnings.
  • Changed: update postcss-custom-selectors reference (with an S)

0.6.2

December 4, 2014

0.6.1

December 1, 2014
  • Changed: update to postcss-calc v3 (which add precision & preserve) & some useless minor updates
  • Changed: standalone version is now uglified (dist/cssnext.js)

0.6.0

November 24, 2014
  • Changed: upgrade to postcss-import v3 which allow to easily consume node_modules
  • Changed: "prefixes" feature is now "autoprefixer"
  • Added: cssnext can be used as a postcss plugin

0.5.0

November 13, 2014
  • Fixed: cssnext returns a string only if the first parameter is a real string (typeof === string)
  • Changed: upgrade to postcss 3
  • Changed: if sourcemap is set to true, default map is now true since postcss v3.0.0 have by default {inline: true, sourceContent: true}
  • Changed: upgrade read-file-stdin from 0.0.4 to 0.2.0

0.4.4

November 11, 2014

0.4.3

November 9, 2014
  • Added: font-variant support (#42)

0.4.2

November 2, 2014
  • Fixed: support !important for custom properties (#12)
  • Added: echo a warning when using a non root custom properties (#13)
  • Added: cssnext can return a postcss instance of no string given (#3)

0.4.1

November 1, 2014
  • Added: gray() support (#44)

0.4.0

October 23, 2014
  • Changed: color feature has been exploded to multiples features (#40).

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
    }
  }
})
  • Changed: cssnext options are not passed to all plugins anymore. You know need to specify feature options by passing object to features properties
    (#39).

Before

//eg: preserve custom properties
var output = cssnext(input, {
  preserve: true
});

Now

//eg: preserve custom properties
var output = cssnext(input, {
  features: {
    customProperties: {
      preserve: true
    }
  }
});
  • Added: more control on sourcemap is possible using the new 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).

0.3.1

August 27, 2014
  • Fixed: nested custom properties usages (#25)

0.3.0

August 26, 2014
  • Added: better custom properties fallbacks (thanks to postcss-custom-properties 0.3.0)

0.2.3

August 26, 2014
  • Fixed: support empty files (#24)

0.2.2

August 22, 2014
  • Fixed: missing bin in npm files...

0.2.1

August 22, 2014
  • Fixed: missing bin in package.json for npm

0.2.0

August 20, 2014
  • Changed: from option doesn't enable sourcemap automatically anymore

0.1.0

August 19, 2014

✨ First release