Dart Sass @import deprecation: how should a mixed @import/@use codebase sequence its migration?
Migration sequencing during the @import deprecation window Dart Sass now emits deprecation warnings for @import (starting around the 1.80 release line) while still compiling it, and the documented replacement is the module system built on @use and @forward . The goal is to migrate a large stylesheet codebase to the module system without breaking builds mid-t
sass