“One year after both Dart Sass and LibSass have launched support for the module system or two years after Dart Sass launches support for the module system, whichever comes sooner (1 October 2021 at latest), we will deprecate @import as well as global core library function calls that could be made through modules.”
At or before this date we should be considering moving to the Sass module syntax.
This will mean removing support for Ruby Sass (which is probably fine) and requiring users to use a version of LibSass or Dart Sass that supports the module system.
This also means we should revisit how we namespace variables, mixins and functions.
Deprecation of @import in Sass
“One year after both Dart Sass and LibSass have launched support for the module system or two years after Dart Sass launches support for the module system, whichever comes sooner (1 October 2021 at latest), we will deprecate @import as well as global core library function calls that could be made through modules.”
At or before this date we should be considering moving to the Sass module syntax.
This will mean removing support for Ruby Sass (which is probably fine) and requiring users to use a version of LibSass or Dart Sass that supports the module system.
This also means we should revisit how we namespace variables, mixins and functions.