Skip to content

Drop support for Ruby Sass and LibSass #2637

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

Open
2 tasks
36degrees opened this issue May 20, 2022 · 2 comments
Open
2 tasks

Drop support for Ruby Sass and LibSass #2637

36degrees opened this issue May 20, 2022 · 2 comments
Assignees
Labels
breaking change documentation User requests new documentation or improvements to existing documentation sass / css

Comments

@36degrees
Copy link
Contributor

36degrees commented May 20, 2022

What

Drop support for Ruby Sass and LibSass, including:

Although there are no code changes, it's highly likely that we'll choose to make related breaking changes as part of this work. Regardless, it's a significant change for our users and so we should treat it as a breaking change.

Why

Ruby Sass was deprecated in April 2018 and reached End of Life in April 2019. We're not aware of any of our users still using it, but as supporting it has involved no extra work on our part we've supported it up until now.

LibSass has also been deprecated since October 2020.

The new Sass module system (@use) is only available in Dart Sass, and there are no plans to introduce it to LibSass. Additionally, a future release of Dart Sass will drop support for @import which will make it impractical for us to continue to support both Dart Sass and LibSass.

Dropping support for LibSass is also a recommendation made by the Sass maintainers themselves:

"We recommend all existing LibSass users make plans to eventually move onto Dart Sass, and that all Sass libraries make plans to eventually drop support for LibSass.

We’re no longer planning to add any new features to LibSass, including compatibility with new CSS features.

LibSass and Node Sass will continue to be maintained indefinitely on a best-effort basis, including fixing major bugs and security issues and maintaining compatibility with the latest Node versions."

Dropping support for Ruby Sass and LibSass will allow us to resolve the following issues:

Who needs to work on this

Developers, technical writer

Who needs to review this

Developers, technical writer

Done when

  • Install docs make it clear that only Dart Sass is supported
  • We no longer test compilation using Ruby Sass and LibSass
@36degrees
Copy link
Contributor Author

There's a presentation with more context on the changes going on in the eco-system, and some of the history of the three different compilers here: https://docs.google.com/presentation/d/10Jf6K-KsqhGyZIjcuxVL6P60ksJ4lSyT96WHZpJwARk/edit#slide=id.g10d42026b8_2_0

We've also started to communicate these upcoming changes to our users in our channels on x-gov Slack and as announcements in the GitHub Discussions for this repo.

@EoinShaughnessy EoinShaughnessy added the documentation User requests new documentation or improvements to existing documentation label May 23, 2022
@EoinShaughnessy EoinShaughnessy self-assigned this May 23, 2022
@EoinShaughnessy
Copy link
Contributor

Re the install docs update - are we removing all mention of LibSass and Ruby Sass, or are we just saying not to use them as we don't support them?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking change documentation User requests new documentation or improvements to existing documentation sass / css
Projects
None yet
4 participants