Breaking Change: Deprecation Version
In the future, it will be an error to pass a Version beyond the current implementation version to Options.fatalDeprecations.
Currently, if you pass a Version that’s greater than the version of the Sass
implementation you’re using, all deprecations will be treated as fatal. This
means that when you upgrade Sass, any new deprecations will also be immediately
fatal. This probably isn’t what you want: you don’t know what behavior will be
deprecated in the future, so this could make any Sass release break your project unexpectedly.
- Dart Sass
- since 3.0.0
- LibSass
- ✗
- Ruby Sass
- ✗
Starting in Dart Sass 3.0.0, passing a Version beyond the current one will be
an error.
Transition PeriodTransition Period permalink
- Dart Sass
- since 1.107.0
- LibSass
- ✗
- Ruby Sass
- ✗
Until Dart Sass 3.0.0 is released, passing a Version that’s too large will
just produce a warning.
If you want to prepare for the upcoming breaking change, the easiest way is just
to pass your current Dart Sass implementation version. If you want to opt into
some future deprecations, you can write code to look for them on the
sass.deprecations record.
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.