Heads up: the Sass legacy JS API will start emitting warnings soon

[nex3]

Goals

Sorry for the template abuse, but I'm filing this on behalf of the Sass team as a heads-up that we're planning to release a version of Sass that begins to emit deprecation warnings for uses of the legacy JS API. Since this is currently the default for Next.js, it might be a good idea to move to using the modern API as the default instead.

Non-Goals

No response

Background

N/A

Proposal

N/A

[iamlinkus]

I'm extremely interested on this getting fixed. Is there a way to force next.js to use the modern api as default as of right now? It doesn't look like we have the ability to set it usingsassOptions.

[mrienstra]

This is the issue to follow: #71638 (already mentioned by @ariesclark)

[ariesclark]

For those looking to silence these errors until Next.js resolves this issue internally.

const nextConfig: NextConfig = {
  sassOptions: {
    silenceDeprecations: ["legacy-js-api"],
  }
}

https://nextjs.org/docs/app/building-your-application/styling/sass and https://sass-lang.com/documentation/breaking-changes/legacy-js-api/#silencing-warnings

Credit to #71638 (comment).