This repository has been archived by the owner on Dec 19, 2024. It is now read-only.
[WIP] postcss-cssnext merge #238
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Now that everything looks "mergeable", the work to be done is to add a good doc on "how to upgrade from cssnext to postcss-cssnext". |
|
Almost ready, I just need to update the features (some are new) in the doc and then merge/deprecations. |
|
👍 nice work |
Closes #215
|
|
||
| ```console | ||
| $ npm uninstall cssnext [--save[-dev]] | ||
| $ npm install postcss postcss-import postcss-url postcss-reporter postcss-browser-reporter postcss-cssnext [--save[-dev]] |
|
Migration documentation is perfect. Good job @MoOx ? |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When ready, this PR will
Closes #173
Closes #174
Closes #175
Closes #180
Closes #191
Closes #192
Closes #199
Closes #207
Closes #214
Closes #225
Closes #231
Closes #237
and finally, closes #230
Since cssnext is now "just" a plugin, this will also closes all the issues related to the tool (cli/api) that are not the responsibility of a plugin:
Closes #73 (see #208 and postcss/postcss#477)
Closes #93
Closes #107
Closes #122
Closes #149
Closes #170
TODO