なつき

The current situation is: 1. Almost none of the most popular sass frameworks have adopted `@use`, because they still want to support both libsass and dart-sass as of today. This...

> One major open question I'm interested in: are there widely-used frameworks other than Vite that still don't support the modern JS API? Or is it the only one? I...

It seems if we don't want to delay this too much, a reasonable solution is to port deprecation options to the legacy API?

> If I'm reading correctly, Next.js [forwards Sass options to sass-loader](https://github.com/vercel/next.js/blob/4515db1e8376f1df84752377d9f50bf42ba0ddcb/packages/next/src/build/webpack/config/blocks/css/index.ts#L175-L185) and so should be configurable to use the modern API although it doesn't by default This actually does not...

On a related note, shall we also mark `sassc-ruby` as end-of-life? The repo has not been updated for 4 years. There are tons of open issues and PRs. Recently, I...

@bolandrm We're planning to deprecate `@import` in favor of `@use`, which libsass does not support. This is a significant change. To prepare for it, we have already marked `node-sass` as...

@ashmaroli PR to add new deprecation options: https://github.com/jekyll/jekyll-sass-converter/pull/164 Please take a look when you get a chance.

Also https://docs.npmjs.com/deprecating-and-undeprecating-packages-or-package-versions

This is a well known bug for the old RubyGems bundled in Ruby 3.1.2. If you upgrade to Ruby 3.1.5, 3.2 or later, it should fix this problem. The root...

@derrickb It would be helpful if you can provide the error stack, in addition to the error message. @nex3 I've quickly searched the code of `rollup-plugin-scss` and I don't see...