| 1 | # postcss-cssnext
|
| 2 |
|
| 3 | [](https://www.npmjs.org/package/postcss-cssnext)
|
| 4 | [](https://travis-ci.org/cssnext/postcss-cssnext)
|
| 5 | [](https://ci.appveyor.com/project/MoOx/postcss-cssnext)
|
| 6 | [](https://gitter.im/cssnext/cssnext)
|
| 7 |
|
| 8 |
|
| 9 | > Use tomorrow's CSS syntax, today.
|
| 10 |
|
| 11 | cssnext is a CSS transpiler that allows you to use the latest CSS syntax today.
|
| 12 | It transforms CSS specs into more compatible CSS so you don’t need to wait for browser support.
|
| 13 |
|
| 14 | ---
|
| 15 |
|
| 16 | # This repository contains the PostCSS plugin.
|
| 17 |
|
| 18 | ## Why **postcss-cssnext** ? What is the difference with **cssnext** ?
|
| 19 |
|
| 20 | cssnext was at first designed to be a complete tool, before PostCSS became
|
| 21 | popular; thus, includes some options that don't really belong in a PostCSS
|
| 22 | plugin (e.g., `import`, `url`, `compress`, `plugins`).
|
| 23 | These days, most people use PostCSS directly so we decided to make integration of
|
| 24 | cssnext more simple by providing a simple (real) plugin.
|
| 25 |
|
| 26 | If you were using cssnext with some options here is what you need to know:
|
| 27 |
|
| 28 | - `import`: just add into your plugins list
|
| 29 | [`postcss-import`](https://github.com/postcss/postcss-import)
|
| 30 | - `url`: just add into your plugins list
|
| 31 | [`postcss-url`](https://github.com/postcss/postcss-url)
|
| 32 | - `compress`: just add into your plugins list
|
| 33 | [`cssnano`](https://github.com/ben-eb/cssnano)
|
| 34 | - `plugins`: just add the plugins directly in your list
|
| 35 | - `messages`: see
|
| 36 | [`postcss-reporter`](https://github.com/postcss/postcss-reporter)
|
| 37 | and
|
| 38 | [`postcss-browser-reporter`](https://github.com/postcss/postcss-browser-reporter)
|
| 39 | - `sourcemap`, `map`, `to`, `from`: see
|
| 40 | [PostCSS source map documentation](https://github.com/postcss/postcss#source-map)
|
| 41 |
|
| 42 |
|
| 43 | ## But I like cssnext as it was !
|
| 44 |
|
| 45 | _Don't worry. That's why we created another package._
|
| 46 | The **cssnext** package will have a major release soon in order to introduce a
|
| 47 | minor but breaking changes in the Node.js API, but you will get the same tool as
|
| 48 | before.
|
| 49 | The nice thing is: **cssnext** will use **postcss-cssnext** under the hood.
|
| 50 |
|
| 51 | ---
|
| 52 |
|
| 53 | ## Check out [cssnext website](http://cssnext.io/)
|
| 54 |
|
| 55 | - [Features](http://cssnext.io/features/)
|
| 56 | - [Setup](http://cssnext.io/setup/)
|
| 57 | - [Usage](http://cssnext.io/usage/)
|
| 58 | - [Playground](http://cssnext.io/playground/)
|
| 59 |
|
| 60 | For questions and support please visit the
|
| 61 | [gitter room](https://gitter.im/cssnext/cssnext).
|
| 62 |
|
| 63 | ---
|
| 64 |
|
| 65 | _The [issue tracker](https://github.com/cssnext/cssnext/issues) is exclusively for bug reports and feature requests._
|
| 66 |
|
| 67 | ---
|
| 68 |
|
| 69 | ## [Changelog](CHANGELOG.md)
|
| 70 |
|
| 71 | ## [License](LICENSE)
|