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.
As stated in #528, node-sass is deprecated in favor of sass. This is causing lots of warnings (due to this breaking change) in projects who consume keen-ui uncompiled SASS components (directly from keen-ui/src/*) and already got rid of node-sass.
So here:
But releasing this means every project who's still trapped in node-sass AND imports the original SASS components (directly from keen-ui/src/*) will not be able to update keen-ui without having to get rid of node-sass too, since new sass modules (i.e. math.div) are not backwards compatible with node-sass.
In return, projects who import the compiled components (most of users to my understanding) or those who import the uncompiled SASS components but already got rid of node-sass, will flawlessly update keen-ui.