[x] I HAVE READ THE FAQ AND MY PROBLEM WAS NOT DESCRIBED THERE
[x] I WILL GIVE 10$ TO CHARITY IF MY SOLUTION WAS ACTUALLY IN THE README/FAQ
Are you trying to transpile a local package or an npm package?
Packages that are in private registries.
Describe the bug
In the previous version of Next.js / next-transpile-modules the following configuration file would build the app successfully and now upgrading both dependencies to the latest ones, the SCSS files are not compiled as they should.
Additional context
So this is impossible to create a reproducible repository since the modules I'm trying to transpile live in private registries but the thing that I find odd is the error message since it appears that now to transpile SASS files the built-in Next.js loaders are being used as well? On Next.js 11.x and next-transpile-modules 8.x this setup worked and now it just breaks in every Sass file.
Also the file that is being errored out is this one - which contains valid SCSS.
Are you trying to transpile a local package or an npm package? Packages that are in private registries.
Describe the bug In the previous version of Next.js / next-transpile-modules the following configuration file would build the app successfully and now upgrading both dependencies to the latest ones, the SCSS files are not compiled as they should.
Setup
next-transpile-modules
version: 9.0.0npm
/yarn
version: NPM x8.0.0Additional context So this is impossible to create a reproducible repository since the modules I'm trying to transpile live in private registries but the thing that I find odd is the error message since it appears that now to transpile SASS files the built-in Next.js loaders are being used as well? On Next.js 11.x and next-transpile-modules 8.x this setup worked and now it just breaks in every Sass file.
Also the file that is being errored out is this one - which contains valid SCSS.
So this leads me to believe that the issue lies in having two css-loaders and two mini-css-extract-plugin apparently being used.