#2334 Disable "DEPRECATION WARNING"s

[Anonymous]

Originally created by: janrembold

We're using gulp-sass package that is only a wrapper for node-sass.

We encounter lots of deprecation warnings like:

DEPRECATION WARNING: Passing a string to call() is deprecated and will be illegal
in Sass 4.0. Use call(get-function("variable-exists")) instead.

This is a valid warning and is related to an old version of Susy Grid. But it is extremely annoying during our development process because it produces hundreds of warnings on each execution of the Sass task.

It would be really great to be able to disable these warnings somehow. Or at least show them only once and not on each execution.

Is there a chance to do that or do you already plan to update this behavior?
Thanks in advance!

[Anonymous]

Originally posted by: fgarcia

After upgrading to 4.9 I am getting lots of these warnings from my dependencies.

I want these warnings if it is in my own code, but I would like to disable them if it is in code I do not control

[Anonymous]

Originally posted by: xzyfer

There's no way for the compiler to differentiate between code you own and code you don't.

These deprecation warnings are important. They're telling you that your code will cease to work very soon, and you should take steps to resolve the warnings asap.

If it's code you don't control then we recommend opening issues on the code's repo, or submitting a PR to resolve the warnings.

There is simply no way to disable these warning. If you don't want to see them I suggest downgrading to an older version of Sass and never updating again.

[Anonymous]

Originally posted by: xzyfer

We'll look at what's involved in deduping the deprecation warnings but we can't make any promises at this time.

[Anonymous]

Originally posted by: igorlakic

I get the same warning when using gulp-sass with SingularityGS... I saw a fix for the same problem in another project - can something like this be a good solution here too?

[Anonymous]

Originally posted by: xzyfer

Yes, this is exactly what needs to be done for the libraries causing these deprecation warnings. It should be easy enough to do for anyone with the time.

[Anonymous]

Originally posted by: esteinborn

@xzyfer I'm wondering if there is a way to print the file that those deprecation warnings are generated from during compilation? I have a large project with many references to functions this way, but only generating a few of the deprecation messages.

[Anonymous]

Originally posted by: xzyfer

So I don't believe we can know the file, and/or location of the offending import for various reasons. However I believe we can at least provide the path and name of the file being imported that is triggering the deprecation warning.

[Anonymous]

Originally posted by: sebszocinski

Any updates on this?

[Anonymous]

Originally posted by: jwahler

@sebszocinski We worked around this issue by updating our susy grid to 2.2.14. All our warnings were produced by susy. Give it a try. good luck.

[Anonymous]

Originally posted by: sebszocinski

Thanks mate

Cheers,

SEB SZOCINSKI
— Web Developer

tel. +61 422 044 127

Apt 1 — 2 East Tce
Adelaide, SA
Australia 5000

ROCKETHOUSE.COM.AU

On Wed, Jun 13, 2018 at 2:37 PM, Joachim Wahler notifications@github.com wrote:
We have work around this issue by updating our susy grid to 2.2.14 [https://www.npmjs.com/package/susy/v/2.2.14] . All our warnings were produced by susy. Give it a try. good luck.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub [https://github.com/sass/node-sass/issues/2334#issuecomment-396814877] , or mute the thread [https://github.com/notifications/unsubscribe-auth/AFNqRuH6BxPyPgCYmFRZ5KnM4e8Y2Ud2ks5t8J4rgaJpZM4TWaDG] .