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

FYI: dartsass-sprockets gem released (upgrade of sassc-rails gem) #38

Closed
johnnyshields opened this issue Feb 3, 2023 · 1 comment
Closed

Comments

@johnnyshields
Copy link

johnnyshields commented Feb 3, 2023

I've released the following gems:

These gems use sass-embedded under the hood, which provides Ruby native interface for Dart Sass.

The SassC gem maintainers were unresponsive so I went ahead and released a gem to benefit Sprockets users. The code is a bit of kludge at the moment. I'd be glad if Rails team wants to take these over, as the current dartsass-rails gem doesn't seem to gel as well (dartsass:watch and all is too much for a troglodyte developer like me to handle 🦖)

(cc: @xfalcox)

@johnnyshields johnnyshields changed the title FYI: dartsass-sprockets gem FYI: dartsass-sprockets gem (upgrade of sassc-rails gem) Feb 3, 2023
@johnnyshields johnnyshields changed the title FYI: dartsass-sprockets gem (upgrade of sassc-rails gem) FYI: dartsass-sprockets gem released (upgrade of sassc-rails gem) Feb 3, 2023
@januszm
Copy link

januszm commented Apr 19, 2023

Does it mean this gem supports assets helpers such as the image-url ? Currently this is a bigger issue with dartsass-rails and requires adding a workaround such as this helper inside an initializer that is shared in many places on the Internet:

class AssetUrlProcessor
  ...

UPDATE: please disregard the above, sprockets-rails+dartsass-rails just solved this issue rails/sprockets-rails#513 (ie. change the image-url to url and it'll use fingerprinted assets)

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

No branches or pull requests

3 participants