-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
_theming.scss deprecation warnings #14636
Comments
I'm not getting any warnings. What version of node-sass are you using? |
4.11.0 |
I tried updating and testing it against our local dev app and a project generated with the CLI, but I wasn't able to reproduce the warning. Can you post the entire warning? Also it seems like the warning is coming from something in the typography utilities, could you post your typography config? |
* Updates to the latest `node-sass` version. * Fixes the build not using the `node-sass` version from the package.json. * Fixes a deprecation warning from the latest SASS version when the consumer has configured a non-string `font-family` (e.g. `Helvetica Neue`). Fixes angular#14636.
fixed |
* Updates to the latest `node-sass` version. * Fixes the build not using the `node-sass` version from the package.json. * Fixes a deprecation warning from the latest SASS version when the consumer has configured a non-string `font-family` (e.g. `Helvetica Neue`). Fixes #14636.
…14673) * Updates to the latest `node-sass` version. * Fixes the build not using the `node-sass` version from the package.json. * Fixes a deprecation warning from the latest SASS version when the consumer has configured a non-string `font-family` (e.g. `Helvetica Neue`). Fixes angular#14636.
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Deprecation warnings when get build
_theming.scss line 1404:
from -> @return if($font-family == null, $font-family, unquote($font-family));
to -> @return if($font-family == null, $font-family, $font-family);
The text was updated successfully, but these errors were encountered: