Breaking Change: type() function
CSS has added a type() function with unique syntax. In order to support flexible syntax for this function, user-defined functions named type() are deprecated.
CSS Values and Units 5 defines a type() function for use in the attr()
function. This function defines the syntax to use when parsing an HTML attribute
as a CSS value, so for example attr(data-count type(<number>)) would return
the value of the data-count attribute as a CSS number. Although it’s currently
only defined in a working draft, Chrome already supports the type() function
so Sass is adding support as well.
Because the type() function doesn’t follow the normal conventions for CSS
expression syntax, Sass will need to parse it as a special function like
url() or element(). Because this represents a breaking change for any
existing Sass code that defined functions named type(), as of Sass 1.86.0 we
are deprecating the ability to define functions with this name. Once this
deprecation has been in place for at least three months, we’ll release a version
of Sass that parses type() as a special function instead.
Can I Silence the Warnings?Can I Silence the Warnings? permalink
Sass provides a powerful suite of options for managing which deprecation warnings you see and when.
Terse and Verbose ModeTerse and Verbose Mode permalink
By default, Sass runs in terse mode, where it will only print each type of deprecation warning five times before it silences additional warnings. This helps ensure that users know when they need to be aware of an upcoming breaking change without creating an overwhelming amount of console noise.
If you run Sass in verbose mode instead, it will print every deprecation
warning it encounters. This can be useful for tracking the remaining work to be
done when fixing deprecations. You can enable verbose mode using
the --verbose flag on the command line, or
the verbose option in the JavaScript API.
⚠️ Heads up!
When running from the JS API, Sass doesn’t share any information across
compilations, so by default it’ll print five warnings for each stylesheet
that’s compiled. However, you can fix this by writing (or asking the author of
your favorite framework’s Sass plugin to write) a custom Logger that only
prints five errors per deprecation and can be shared across multiple compilations.
Silencing Deprecations in DependenciesSilencing Deprecations in Dependencies permalink
Sometimes, your dependencies have deprecation warnings that you can’t do
anything about. You can silence deprecation warnings from dependencies while
still printing them for your app using
the --quiet-deps flag on the command line, or
the quietDeps option in the JavaScript API.
For the purposes of this flag, a "dependency" is any stylesheet that’s not just a series of relative loads from the entrypoint stylesheet. This means anything that comes from a load path, and most stylesheets loaded through custom importers.
Silencing Specific DeprecationsSilencing Specific Deprecations permalink
If you know that one particular deprecation isn’t a problem for you, you can
silence warnings for that specific deprecation using
the --silence-deprecation flag on the command line, or
the silenceDeprecations option in the JavaScript API.