Ruby Sass End-of-Life: 26 March 2019
chriseppstein opened this issue · comments
This was announced about a month ago, but I wanted to make sure the Rails community is aware that the Ruby implementation of Sass has been EOL'd.
TL;DR:
- The reference implementation of Sass is now written in Dart.
- Ruby Sass is maintained for security and CSS Compatibility issues through March 2019.
- Only PRs for the above mentioned reasons are being accepted at this time.
- The git repo for ruby sass is now officially at https://github.com/sass/ruby-sass
- The repo at https://github.com/sass/sass is now for implementation-agnostic language issues.
- On 26 March 2019, the deprecation period for Ruby Sass will end and it will no longer be maintained.
That is, unless, there's at least one new, active maintainer for the ruby implementation of Sass. Preferably more than one.
Rails needs a plan a plan to deal with this before the ruby version becomes unmaintained. If a first-class Sass implementation for the ruby and rails community is desired, hopefully a maintainer can be found. Otherwise, one of the other Sass implementations can be used (most likely through node/npm).
any progress here?
SassC requires CRuby
Generating a new default Rails 5.2 app gets you this deprecation warning.
March 2019 is coming up, is there any news on what is expected?
I personally started switching to Webpacker.
Migration of existing apps it is pretty easy and it will be the default Javascript compiler in Rails 6.
Migrating CSS is even easier than migrating JS. I leave here a guide to do that.
I hope it will help someone else.
@coorasse I need simple css file for each page, not bundle, Sprockets do that easy, with Webpack this is no trivial task
Not for all sites need react and not all sites are SPA
Maybe sassc-rails should be used as a drop-in replacement for sass-rails? I have the impression it should be pretty easy to change that on rails generators.
Ok
now I see the thread on rails main repo and it seems its not possible to simple replace sass-rails with sassc-rails. So migrate to webpacker seems to be the way to go.
@amalrik can you link to the thread on rails main repo for us?
In my specific apps, I have switched to sassc-rails without problem. Although I have no trouble believing there are reasons it can't work universally. I am curious to see what is being discussed on rails repo.
They are still contemplating simply replacing the sass processor with the sassc processor in sass-rails it seems: rails/rails#34884 (comment)
thanks @P9GIT
I will take a look if I can contribute to that in some way.
See #424
Awesome! Thanks!