-
Notifications
You must be signed in to change notification settings - Fork 357
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
Quiet-deps flag still showing "Global built-in functions are deprecated and will" deprecation warning (not others) #2418
Comments
Can you provide a repo that can reproduce this? |
We've run into the same issue, would be great to have this fixed in the next release! Minimal example for reproducingpackage.json: {
"dependencies": {
"foundation-sites": "^6.9.0",
"sass": "^1.81.0"
}
} style.scss: @import "foundation-sites/scss/foundation";
@include foundation-everything; CLI: Expected output1 deprecation warning for using Actual outputLots of additional deprecation warnings for global built-in functions somewhere in foundation’s scss. |
This may help
EDIT: #1360 (comment) |
@katzmo Thanks for the reproduction. It looks like our internal tracking of dependency status got screwed up by @raph5 That reproduction has nothing to do with |
Hey, annoyingly we're unable to upgrade our third party dependencies for the time being but would love to get our frontend working with the latest version of dart-sass 1.8.*
We're currently running our sass built script as so
sass --load-path=./node_modules --quiet-deps scss/uos.scss css/uos.css
This works great and the dependencies don't throw warnings like they do when omitting
--quiet-deps
however, we do still seem to get this error coming through.This only seems to happen with this specific deprecation warning
Global built-in functions are deprecated and will be removed in Dart Sass 3.0.0.
I can't seem to find out why this is happening looking through the docs. I'm aware I can add the flag
--silence-deprecation
for the above warning, but I would ideally like to keep this for our code (just not the third party dependencies)Thank you, and apologies if I've missed anything.
The text was updated successfully, but these errors were encountered: