-
Notifications
You must be signed in to change notification settings - Fork 104
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
Upgrade sassc to avoid SIGABRT (code 134) in rake task #171
Comments
FYI forcing sassc to an updated version solved this problem.
|
FYI I'm maintaining dartsass-sprockets which is a fork of this gem. You can try it and see if your issue is resolved; it uses a different engine (Dart Sass) under-the-hood, so these FFI issues should go away. |
your dartsass-sprockets doesn't compile with bootstrap 5.3 and Rails 7.1, so I wouldn't recommend it. |
@creiterer04 You can raise a ticket to dartsass-sprockets with details and I'll take a look. The compile errors should be trivial, and may in fact be due to Bootstrap's SASS using syntax which is not compliant with the latest Dart SASS. Myself and others are using dartsass successfully with Bootstrap today. SassC is dead--the SASS maintainers are no longer supporting it. I put dartsass-sprockets out there to help folks, but if it doesn't work for you, to each his/her own. |
We are getting the following exception in CI during bundler operations. It appears this may be due to an sassc issue. Forcing the
sassc
version to latest appears to fix the issue for us.Should
sassc-rails
issues a new release with updatedsassc
version so others don't have to run into this?The text was updated successfully, but these errors were encountered: