Next.js: ValidationError: Invalid options object. CSS Loader has been initialised using an options object that does not match the API schema

[wellyshen]

Bug report

Describe the bug

When upgrade to v9.0.7. css-loader throw an API schema error. It won't happens in v9.0.6. Seems minimize has been removed from the options of css-loader (see here)

To Reproduce

1. yarn upgrade next.js@^9.0.7
2. yarn dev

Expected behavior

app compiled success

Screenshots

System information

• OS: macOS
• Browser: chrome
• Version of Next.js: 9.0.7

[timneutkens]

Duplicate of https://github.com/zeit/next-plugins/issues/541

Will keep it open there as this doesn't relate to Next.js internals.

[macrozone]

@timneutkens be aware that because next 9.0.7 now forces css-loader 3.2.0, anyone that uses @zeit/next-css will run into that issue. So i think it should be top priority. I would also like to see a migration path from css-loader to the new experimental css feature.

[timneutkens]

Joe opened https://github.com/zeit/next.js/pull/8944

[CezarMocan]

+1, happening with @next/less for me.

[Timer]

Please try [email protected] -- this version should fix these broken plugins.

[retallicka]

I got this error using 9.0.7 and @zeit/next-sass, 1.0.1 when I upgrade to [email protected] I get Module not found: Can't resolve 'css-loader/locals'

[Timer]

@retallicka please provide a reproduction.

[Timer]

@retallicka a fix should be up in https://github.com/zeit/next.js/pull/8957; I found the source of this loader.

[Timer]

Please give v9.0.8-canary.4 a try.

[dbedoyat]

Works well with [email protected] and [email protected]

[nns2009]

I confirm for 'next-sass'
"@zeit/next-sass": "^1.0.1"
produced the same error with [email protected],
but works with [email protected]