-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Deprecation warnings about SASS darken() #1541
Comments
Hi @djvill, thanks for submitting an issue! I appreciate its thoroughness - makes it very easy to reproduce :) To confirm, in a recent version of sass (1.79.0), they have deprecated the In the meantime, if you urgently need to silence the deprecation warnings, your best bet is to freeze your sass version to 1.78.0 in your |
Thanks @mattxwang! |
just ran into this also:
|
Ah - okay, slightly bad news. Users of the I will have to think about a way to resolve this issue in the general case. I think it's unlikely I will push a fix very quickly (especially as my bandwidth has been awful recently). My suggestion is to either:
sass:
quiet_deps: true Sorry for the confusion! Unfortunately, a general solution is slightly out of my hands unless we drop support for |
Hi @mattxwang, just following up to mention that pinning my |
Describe the bug
When I build my site locally, I get deprecation warnings about SASS
darken()
. (See https://sass-lang.com/documentation/breaking-changes/color-functions/.) These warnings point to just-the-docs SASS files; none of my custom SASS files includedarken()
.To Reproduce
Steps to reproduce the behavior:
Site builds correctly, but bash output includes a whole bunch of deprecation warnings:
Expected behavior
Site builds locally without warnings.
Screenshots

Desktop (please complete the following information):
Additional context
This issue doesn't occur when I build the
just-the-docs
site locally, so it must be something with how my site is configured. It also didn't occur with just-the-docs version 0.7.0The text was updated successfully, but these errors were encountered: