Deal with the consequences of https://sass-lang.com/d/import

[pradyunsg]

What's happening?

Sass has deprecated @import, something that Furo relies on fairly heavily. The automated migration tool does not work for how Furo's code is layed out / built, so... I'll likely need to change how the styles are built.

Reproducer

1. Build with stb compile
2. Notice the deprecation warnings.

Expectation

No deprecation warnings.

This was requested by a maintainer.

• I was asked to open an issue in a discussion by a maintainer.

Code of Conduct

• I agree to follow the Code of Conduct.

[sveetch]

Hi, Bootstrap has done the transition to remove 'import' rule in profit of use/forward rules and migrated to the Sass builtin modules, there is a huge commit in a development branch:

twbs/bootstrap@9e28b85#diff-faf5c61d83af49020af8943c05226ca59b56525abac2c3c29298def71d9bea81

As a resume:

To restore the basic @import behavior to include the CSS rules like .foo {content: "plop";} from a _the_module.sass module just use @use the_module;.

To include mixins for usage you can use a joker like @use "foo" as *;, every functions, variables and mixins from _foo.sass module will be callable directly without any prefix.

If you just use @use foo; your functions, variables and mixins will need to be called with the module name as a prefix like foo.myfunction();.

Except the import/use rules you won't need to rewrite your Sass modules.