Sass modern compiler future deprecation warnings

[silvenon]

I'm not sure how you're doing it, I've tried to figure it out from the source code, but when installing sass-embedded and configuring api: "modern-compiler" for Sass I'm getting future deprecation warnings by default.

I don't mind this necessarily, but I'm wondering whether there is something special that you're doing that's enabling this, because in Sass docs I seem to need to enable future deprecation warnings explicitly, each one either by name, or by id, I'm not able to just enable all of them.

I'd love to know how to do this via CLI, whatever it is that Vite is doing. But Vite enabling all future deprecation warnings can be unexpected to people who've used Sass via CLI, and might not know how to disable that, or that they can disable it at all.

Btw, what is api: "modern-compiler" doing vs. api: "modern"?

---

I don't expect an answer to any of this, this is still intended as feedback.

[hi-ogawa]

Btw, what is api: "modern-compiler" doing vs. api: "modern"?

Answering this first, basically sass provides three variants of programmatic API https://sass-lang.com/documentation/js-api/modules/. Vite exposes these three modes by mapping api:

• modern: compileStringAsync
• modern-compiler: initAsyncCompiler
• legacy: render

modern vs modern-compiler is purely for optimization of sass API level. For legacy vs modern/modern-compiler, Sass seems to have a different implementation and features internally (so the behavior around what to warn or not might change between legacy and modern).

I'm not sure how you're doing it, I've tried to figure it out from the source code, but when installing sass-embedded and configuring api: "modern-compiler" for Sass I'm getting future deprecation warnings by default.

I'm not sure if Vite is doing something special. If you want to silence warning, you can use Vite's config css.preprocessorOptions.scss/sass https://vite.dev/config/shared-options.html#css-preprocessoroptions, which is going to passed to sass's programatic API options. What they support exactly can be found on their doc https://sass-lang.com/documentation/js-api/interfaces/stringoptions/ and https://sass-lang.com/documentation/js-api/interfaces/legacystringoptions/

[silvenon]

Yeah, I'm aware that I can silence the warnings there, but I need to list all of them there. I guess via sass-embedded's Node.js API they get all enabled by default somehow because I see that Vite doing anything to enable them (that wouldn't make sense anyway).

I'm in a position where I'm migrating my app to Vite, so I'd like to create Sass migrations as a separate PR considering these circumstances, but simply installing sass-embedded isn't creating these deprecation warnings, however I'm going to find a different migration path.