Update postcss-cssnext to the latest version 🚀 #16
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.
Version 3.0.0 of postcss-cssnext just got published.
The version 3.0.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of postcss-cssnext.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Release Notes
3.0.0Removed: support for node 0.12
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:
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
Commits
The new version differs by 11 commits.
03b6017
3.0.0
cf9fb19
Docs: fix chalk update issue
b7d6ffd
Merge pull request #400 from MoOx/postcss6-upgrade
1781dc7
Docs: Fix id of overflow wrap property in index (#393)
8b99180
Ensure a version of caniuse-db that includes css-image-set (#380)
db0f0fa
Add a warning for custom property sets that are going to be removed + an option to hide the warning
cc7c864
Change: support node4+ up to 8
7bb55c1
chore: add package-lock.json and yarn.lock files
20ae74d
Change: upgrade to PostCSS 6
af5f9c1
Change link to custom media queries specification
974e40b
Fix PR link
See the full diff
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴