Update postcss-cssnext to the latest version 🚀 #71
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
![greenkeeper[bot]](https://avatars.githubusercontent.com/in/505?s=60&v=4){kind=small}
Version 3.0.1 just got published.Update to this version instead 🚀 Release Notes3.0.1CommitsThe new version differs by 5 commits.
See the full diff |
Version 3.1.0 just got published.Update to this version instead 🚀 Release Notes3.1.0CommitsThe new version differs by 17 commits.
There are 17 commits in total. See the full diff |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
@applyThis 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.
03b60173.0.0cf9fb19Docs: fix chalk update issueb7d6ffdMerge pull request #400 from MoOx/postcss6-upgrade1781dc7Docs: Fix id of overflow wrap property in index (#393)8b99180Ensure a version of caniuse-db that includes css-image-set (#380)db0f0faAdd a warning for custom property sets that are going to be removed + an option to hide the warningcc7c864Change: support node4+ up to 87bb55c1chore: add package-lock.json and yarn.lock files20ae74dChange: upgrade to PostCSS 6af5f9c1Change link to custom media queries specification974e40bFix PR linkSee 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 🌴