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
Dart Sass 2.0.0 support: "Using / for division is deprecated and will be removed in Dart Sass 2.0.0." #436
Comments
There is a migration tool that can help with that. |
@fuhlig Nevertheless, wouldn't it be better to use the valid syntax with sass:math? |
Definitely! My comment was not for Inuit users to migrate their existing codebase to fix warnings in Inuit but for Inuit Devs/Contributors to fix it on the framework level. |
Current release is 4 years old. There is a nonzero chance of this ever getting fixed, but it's probably still very close to zero 😞 |
You could create a PR or fork it an fix it yourself, @thany 🙂 |
Absolutely true. Guess what I did: thany/inuitcss-dart 😎 |
Would @csswizardry consider some PRs to fix the now deprecated Inuit repos where this Dart Sass deprecation comes up? The 2 issues that are raised seem simple to fix. If not, I'll just patch it myself. Problem is I have a huge project using this and there's no good reason to rewrite it. |
For future visitors of this thread, If you want to use the inuitcss with dart-sass I published an npm package for that purpose. The node-sass dependency has been replaced by dart-sass. and the SCSS files were updated to change the |
Hey there,
We have been using Inuit for 6 years now, and recently moved over to Dart Sass, away from Node Sass.
Dart Sass is throwing some deprecation warnings for the
/
division operator:As LibSass (and therefore NodeSass) is now deprecated (https://sass-lang.com/blog/libsass-is-deprecated), I am wondering what the main contributors thoughts are on if Inuit should be looking to migrate to Dart Sass?
The following is directly from the libsass-is-deprecated article:
The text was updated successfully, but these errors were encountered: