How to disable these 10k sass warning in my very old app?

[CaptainN]

Summary

I'm getting literally thousands of sass deprecation warnings in my console after updating to next 15 in a very old code base. I don't want to ever have to update the hundreds, or maybe thousands of sass files. I'd rather use very old sass builds. Is there a way I can opt out of dart-sass? The old one works just fine. There's literally no reason to update it.

If there is just some way to disable the warning, that'd be great too. I tried a bunch of variations of this, but none of them have ANY effect:

sassOptions: {
    includePaths: [path.join(__dirname, "src")],
    silenceDeprecations: ["legacy-js-api"],
    implementation: "sass-embedded",
  },

Additional information

I also tried just searching the docs for the right settings - but there is no search!! There is only that utterly useless v0 input box. Can we please get back a regular old token search for the API docs? Thanks.

Example

No response

[CaptainN]

I think I may be mixing up the deprecation errors I'm seeing, which are from dart-sass imposing new "features" on sass, like replacing @import with MUCH more cumbersome @use and @forward. Oye. Is there some way I can just configure next.js's webpack to use the old one (which again, works fine - I don't need any new fangled features.)

[CaptainN]

Ugh, this ended up being SUPER easy to work around, there's just a lot of red herrings when searching for this. The Deprecation warnings that config item talks about having nothing to do with the ones I'm seeing.

I just pinned sass and sass-loader to an older version (1.33 and 10.1.1) and it seems to work for now. This is probably a ticking time bomb, but at least it's working.

[venn24]

Tks u so much.