You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are also, some dependencies that are using still a deprecated version.
npm WARN deprecated [email protected]: It's deprecated, please use postcss-scss instead.
npm WARN deprecated [email protected]: cssnext is now postcss-cssnext. cssnext is deprecated. See postcss-cssnext migration guide http://cssnext.io/postcss/
npm WARN deprecated [email protected]: cssnext is now postcss-cssnext. gulp-cssnext is deprecated. Use gulp-postcss instead. See postcss-cssnext migration guide http://cssnext.io/postcss/
Is there a reason why we keep them out of date? If not, I can prepare a PR.
The text was updated successfully, but these errors were encountered:
@DanielaValero Hi! As far as I remember, no reason. You can update, just check with tests that everything is working. PR is very much appreciated, thank you!
Sure, I already started some work on the matter, and for sure will take some more time as the angular one. But will get it in :)
Also, with the latest version of KSS, I think we will be able to support words instead of numbers for the sections.
I will make sure to update readme accordingly, and letting you know with time, if there is any breaking change, so we can announce it accordingly to the users
Hello,
There are some dependencies in the project that are quite out of date. Here the list
There are also, some dependencies that are using still a deprecated version.
Is there a reason why we keep them out of date? If not, I can prepare a PR.
The text was updated successfully, but these errors were encountered: