Skip to content
This repository was archived by the owner on Dec 19, 2024. It is now read-only.

Commit c706ef7

Browse files
pensierinmusicaMoOx
authored andcommitted
Update README.md
Closes #215
1 parent ace4a48 commit c706ef7

File tree

1 file changed

+11
-0
lines changed

1 file changed

+11
-0
lines changed

README.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,12 +17,23 @@ It transforms CSS specs into more compatible CSS so you don’t need to wait for
1717

1818
## Why **postcss-cssnext** ? What is the difference with **cssnext** ?
1919

20+
### Short answer
21+
22+
If you're using PostCSS in your build process, and want to add cssnext, you need only `postcss-cssnext`
23+
(check the "options" section here below).
24+
Otherwise, if you like cssnext to work as a full standalone package with its own cli
25+
(independently of PostCSS), use `cssnext`.
26+
27+
### More details
28+
2029
cssnext was at first designed to be a complete tool, before PostCSS became
2130
popular; thus, includes some options that don't really belong in a PostCSS
2231
plugin (e.g., `import`, `url`, `compress`, `plugins`).
2332
These days, most people use PostCSS directly so we decided to make integration of
2433
cssnext more simple by providing a simple (real) plugin.
2534

35+
### Options
36+
2637
If you were using cssnext with some options here is what you need to know:
2738

2839
- `import`: just add into your plugins list

0 commit comments

Comments
 (0)