0

I am trying to suppress/fix a deprecated warning from my grunt-sass (based on node-sass) compile that I traced to Susy 2 using functions listed to deprecate in Sass 4.0. At this point, it's not feasible to upgrade to Susy 3 as there's no upgrade guide and will break a large website.

Node-sass offers a --quiet option that I've passed in my Gruntfile.js though I am still getting the warning. This is my SASS section in my Gruntfile.js.

sass: {
    options: {
        quiet: true,
        sourceMap: false,
        outputStyle: 'compressed'
    },
    dist: {
        options: {
            quiet: true 
        },
       files: {
           'static/css/style.min.css' : 'static/css/sass/style.scss',
           'static/css/orderform.css' : 'static/css/sass/orderform.scss'
       }
    }
}

Is there a way to suppress deprecated warnings? Just ignoring the warnings will slow down my development, outputting all the warnings increases my compile time from ~1s to ~4s.

Here is the log output

l3fty
  • 572
  • 3
  • 16
  • 1
    What minor version of Susy 2 are you using? Version 2.2.14 was specifically released to solve this problem. If you are on 2.2.14 and still getting the warnings, can you paste them here or file an issue on github? – Miriam Suzanne Aug 06 '18 at 20:15
  • Hi @MiriamSuzanne, I am not sure what version it was but I switched to npm and installed Susy 2.2.14 then compiled from that but still getting deprecated warnings. I've edited my OP and added a Gist of the log output. Looks like only two functions are causing the warnings, `mixin-exists` and `variable-exists`. – l3fty Aug 07 '18 at 08:53
  • 1
    That's very strange, because [we definitely use `get-function()` to capture functions](https://github.com/oddbird/susy/blob/susytwo/sass/susy/output/support/_support.scss#L73) in that release. I tried to reproduce this locally, but I'm not able to. I do get the warning when I write an improper `call()` - but I'm not able to get the same warning from Susy that you see. Are you sure the version of Susy being used is the version in npm? – Miriam Suzanne Aug 08 '18 at 16:17
  • You were absolutely correct, @MiriamSuzanne. I was compiling two SASS files one of which I forgot to correct the new Susy path. **No more deprecated warnings after upgrading to 2.2.14.** If you want to add the answer to this question I'll be happy to mark it correct. – l3fty Aug 14 '18 at 07:12

1 Answers1

2

Version 2.2.14 was specifically released to solve this problem. I tried to reproduce this locally in 2.2.14, but I'm not able to. I do get the warning when I write an improper call() - but I'm not able to get the same warning from Susy. Are you sure the version of Susy being used is the version in npm?

Miriam Suzanne
  • 13,632
  • 2
  • 38
  • 43