next-css 0.2.1-canary.4 incompatible with Next.js 9.0.7

[samcx]

Bug Report

I have been using the canary version of zeit@/next-css because version 1.0.1 does not minify my CSS chunk in production.

After upgrading to Next.js 9.0.7, I receive this error when starting my application using the now dev command or using the script 'dev': 'next' ->

I was able to reproduce my error on a blank slate Next.js application with the same dependencies:

• @zeit/next-css: ^0.2.1-canary.4
• next: 9.0.7
• react: 16.10.1
• react-dom: 16.10.1
  ...
• now-cli: 16.3.0

Previous Next.js versions (9.0.6 and lower 9 versions) have been working flawlessly.

System Information

• OS: MacOS Mojave Version 10.14.6
• Browser: Chrome 77.0.3865.90 (Official Build) (64-bit)

[brycejacobs]

Same issue after upgrading to 9.0.7.

[nghiepdev]

Same issue https://spectrum.chat/next-js/general/next-9-0-7-and-zeit-next-sass-error~8a54bc3b-9a57-4e7d-8383-d162f2ced59f

[Timer]

Please try next@9.0.8-canary.4 -- this version should fix these broken plugins.

[kachkaev]

@cuonghv91 what is the error that you see in next@9.0.8-canary.3?

[cuonghv91]

Hey folks !
It works perfect on next@9.0.8-canary.3.
Thanks @Timer

[samcx]

Still getting the same error message with the canary version @zeit/next-css@0.2.1-canary.4, for next@9.0.8-canary.3 to next@9.0.8-canary.5 and next@9.0.8. zeit/next-css@1.0.1 does work with the 9.0.8 versions.

I don't understand why the stable version (zeit/next-css@1.0.1) does not minify CSS? Was this a design choice?