This version 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 cssnano.
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.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
cssnano will no longer console.warn any messages when using deprecated
options; these are now sent to PostCSS. You will be able to see them if you
use a PostCSS runner with built-in messages support, or alternately by
loading postcss-reporter or postcss-browser-reporter in your plugins list.
Prepares support for grid identifier reduction by adding it to the list
of optimisations turned off when options.safe is set to true.
Adds support for normalizing unicode-range descriptors. Values will
be converted when the code matches 0 & f in the same place on both sides
of the range. So, u+2000-2fff can be converted to u+2???, but
u+2100-2fff will be left as it is.
Hello lovely humans,
cssnano just published its new version 3.10.0.
This version 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 cssnano. 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.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
GitHub Release
console.warnany messages when using deprecated options; these are now sent to PostCSS. You will be able to see them if you use a PostCSS runner with built-in messages support, or alternately by loadingpostcss-reporterorpostcss-browser-reporterin your plugins list.grididentifier reduction by adding it to the list of optimisations turned off whenoptions.safeis set totrue.unicode-rangedescriptors. Values will be converted when the code matches0&fin the same place on both sides of the range. So,u+2000-2fffcan be converted tou+2???, butu+2100-2fffwill be left as it is.The new version differs by 81 commits .
355c6ec3.10.03616279Update changelog.64a25c6Normalize unicode-range descriptors.3321f85Add grid reduction to the safe options.9156e8dReplace deprecation logging with PostCSS messages.51e3e1dTidy up API tests.30cd948Update module tests to reflect changes in postcss-normalize-url.5d28cbfUpdate for postcss-minify-selectors@2.1.0.e1e656eFix install links on the homepage.406e27aUpdate tests for postcss-svgo@2.1.6.83ce0beUpdate for postcss-minify-params@1.1.0.99fa8e3Fix phenomic build.0f700f1Add copy to clipboard buttons for usage. Closes #305.2be47f1Update remark-behead for remark 6 compatibility.e0aaac6Add --global to the docs.There are 81 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade