Should using SCSS Modules be forced?

[pooyarm]

What version of Next.js are you using?

10.2.3

What version of Node.js are you using?

16.9.0

What browser are you using?

Chrome

What operating system are you using?

macOS

How are you deploying your application?

Other platform

Describe the Bug

We have a not small product which contains hundreds of components. We've migrated to Nextjs almost 3 years ago, before that we were LESS and one reason that we decided to use Nextjs was that it was supporting LESS. But nowdays it doesn't support LESS for the favour of SCSS, which is good, we decided to migrate to SCSS, but then we realized Nextjs forces us to use SCSS Modules! Using SCSS Modules is nice, but refactoring hundreds of components need a lot of effort and time which is not possible in practice.

So the problem is that forcing to use SCSS Modules will block products like us to continue with Nextjs.

You may say this is not a bug and just ignore it, but I already asked on Discussions but got no reply after months. I hope I get a reply this time.

Expected Behavior

A possible solution would be making SCSS Modules optional and enabled by default.

To Reproduce

[danoc]

Would this solve your problem? #27953

[pooyarm]

@danoc Yes, I think so, I've also commented there, maybe they decide about it. Thanks

[timneutkens]

This is tracked in #27953 indeed, please upvote it there using 👍

[balazsorban44]

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.