next build doesn't build CSS into output directory.

[chilijung]

Bug report

Issue move from vercel/next.js#4845

Describe the bug

When using @zeit/next-css in next.config.js, in dev mode the CSS successfully built into .next/static/style.css but when using next build to build static version of the app will not generate .next/static/style.css in the directory.

To Reproduce

You could reproduce this error in this demo https://github.com/Canner/canner-demo/tree/master/nextjs-ecom-with-firebase

next.config.js is located: https://github.com/Canner/canner-demo/blob/master/nextjs-ecom-with-firebase/functions/next.config.js

Steps to reproduce the behavior, please provide code snippets or a repository:

1. run npm run dev in dev mode css is generated.

2, run ./node_modules/.bin/next build css is NOT generated in output directory.

Expected behavior

When entering next build in output folder it should also generate CSS files.

System information

• OS: [e.g. macOS, Windows]: mac
• Browser (if applies) [e.g. chrome, safari]: chrome
• Version of Next.js: [e.g. 6.0.2]: 6.1.1

Additional context

Add any other context about the problem here.

[gate3]

I am currently having issues with mini-css-extract-plugin. I installed @zeit/next-css and i tried importing the css as modules as described in the repo, but i keep getting this error:

Module build failed (from ./node_modules/mini-css-extract-plugin/dist/loader.js):
ModuleParseError: Module parse failed: Unexpected character '' (1:0)
You may need an appropriate loader to handle this file type.

I tried the canary version as well without success.

My current versions are:

"@zeit/next-css": "^1.0.1",
"next": "7.0.2",
 "react": "16.6.1",
 "react-dom": "16.6.1"

I also tried just including the css with href links in the head in the _app.js file that didn't work as well. Any help will be greatly appreciated.

[kachkaev]

@gate3 can you try @zeit/next-css@1.0.2-canary.2 (released just a few hours ago)? Sharing a minimal working example would be useful too. Feel free to open a new issue once you’ve created a small example project and the error still appears there.

[gate3]

@kachkaev thanks. Will try that and if it doesn't work will make a repo

…

On Thu., 15 Nov. 2018, 8:24 am Alexander Kachkaev ***@***.*** wrote: @gate3 <https://github.com/gate3> can you try @***@***.*** (released just a few hours ago)? Sharing a minimal working example would be useful too. Feel free to open a new issue once you’ve created a small example project and the error still appears there. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#226 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADbkfYFmK8ne-i3yXYH1fCxxzGesqe3xks5uvRamgaJpZM4Vhkrp> .