Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove SASS deprecation warnings #529

Merged
merged 1 commit into from
Aug 6, 2022
Merged

Remove SASS deprecation warnings #529

merged 1 commit into from
Aug 6, 2022

Conversation

desko27
Copy link
Contributor

@desko27 desko27 commented Sep 15, 2021

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:

  • node-sass is removed in favor of sass
  • All deprecation warnings are fixed the recommended way

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.

@JosephusPaye
Copy link
Owner

Thanks!

The backward compatibility issue is an interesting one. Perhaps this can be released with a tag in the version, for those who have made the switch.

@desko27
Copy link
Contributor Author

desko27 commented Sep 21, 2021

The tag thing seems good to me. How can I help here?

@desko27
Copy link
Contributor Author

desko27 commented Sep 22, 2021

Adding a bit more detail on this as I missed an important point (I updated the PR description to reflect it).

Summary of story

We're importing the uncompiled SASS components for SASS var customization purposes. That's what's causing the SASS warnings. But importing the named exports just from keen-ui is not causing SASS warnings as those components are actually CSS.

Actual breaking changes

Given that, the users who would receive a "breaking change" from this PR would be the ones who are already importing the uncompiled SASS components directly from keen-ui/src/* like us, and still didn't get rid of node-sass.

@olsgreen
Copy link
Contributor

olsgreen commented Aug 1, 2022

@desko27 Nice work, our build screens look much nicer now!

@JosephusPaye Can we get this merged, if you are concerned over the backwards compatibility and want to stay true to semantics just bump the major? Also, would be great to chat to you about the future of this project. We've had great use out of it for a number of years now, I'd hate to see it not move forward, but also realise that you have other commitments. We may be able to help in a few different ways, please just reach out to me.

@JosephusPaye
Copy link
Owner

Hi all, I'll try to get this merged and released soon.

@olsgreen Happy to have a chat about this. I'd love to see the library continue to evolve and be maintained, as I currently use it in production projects myself.

@JosephusPaye JosephusPaye merged commit e033396 into JosephusPaye:next Aug 6, 2022
@JosephusPaye
Copy link
Owner

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants