Erroneously seeing the warning: "... deprecation is obsolete, so does not need to be made fatal."

[u01jmg3]

Previously, @nex3 was kind enough to provide the following code to exclude certain deprecations.

const sass = require('sass');

const deprecationIds = Object.keys(sass.deprecations);
const excludedDeprecations = ['import'];
const includedDeprecations = deprecationIds.filter(id => !(new Set(excludedDeprecations)).has(id));

sass.compileString(
  '@import "other"', 
  { silenceDeprecations: excludedDeprecations, fatalDeprecations: includedDeprecations }
);

This worked without issue. However, I am now seeing the following unexpected warnings:

Warning: mixed-decls deprecation is obsolete, so does not need to be made fatal.

Warning: type-function deprecation is obsolete, so does not need to be made fatal.

Although it shouldn't be necessary, adding mixed-decls and type-functions to silenceDeprecations removes the previous warnings, but now causes the following:

Warning: mixed-decls deprecation is obsolete. If you were previously silencing it, your code may now behave in unexpected ways.

Warning: type-function deprecation is obsolete. If you were previously silencing it, your code may now behave in unexpected ways.

Ideally, I would expect deprecations that are obsolete not to be included by Sass.

[nex3]

If obsolete deprecations weren't included at all, that would mean that any time we made a deprecation obsolete it would be a breaking change in the JS API because that field would vanish on sass.deprecations. We want to make sure it's possible to pass the same options across Sass versions (and potentially implementation) without lots of breakages, and that means keeping around old deprecations. Bear in mind that what you're doing here is already a bit off the beaten path.

You can look at Deprecation.status to omit obsolete deprecations from includedDeprecations, which should fix your immediate issue.