next.js: [9.3] CSS Modules cannot be imported from within node_modules
Bug report
Trying to migrate to next 9.3 and using the built-in sass feature. When trying to use CSS modules with next 9.3, all my modules trigger the warning
./src/components/Footer/Footer.module.scss
CSS Modules cannot be imported from within node_modules
./src/components/Footer/Footer.module.scss
Module build failed: Error: Final loader (./node_modules/next/dist/build/webpack/loaders/error-loader.js) didn't return a Buffer or String
Describe the bug
I’m trying to properly migrate to Next 9.3 and use the built-in sass feature. When I have a file named *.module.scss (not even imported), I have warnings in the terminal saying that CSS Modules cannot be imported from within node_modules..
To Reproduce
- Remove
@zeit/next-sassfromnext.config.jsandpackage.json - Remove .next folder
- Add saas
npm install sass - Create a file
Something.module.scss. No need to import it. - Note the warnings in the terminal
Expected behavior
No warning should popup in the terminal.
System information
- OS: macOS Mojave 10.14.6
- Version of Next.js: 9.3.0
- Version of Node: 13.9.0
- Version of npm: 6.13.7
Additional context
I have updated next.config.js to be able to use the importing convention ~/ instead of ../
next.config.js
const path = require('path');
module.exports = {
webpack: config => {
// Alias
config.resolve.alias['~'] = path.resolve(__dirname + '/src');
return config;
}
};
package.json
{
"name": "...",
"version": "0.1.0",
"description": "...",
"main": "index.js",
"scripts": {
"dev": "next dev",
"build": "next build",
"start": "next start"
},
"keywords": [],
"author": "...",
"license": "MIT",
"dependencies": {
"@contentful/rich-text-react-renderer": "^13.4.0",
"@optimizely/react-sdk": "^1.1.0",
"bootstrap": "^4.4.1",
"contentful": "^7.14.0",
"isomorphic-unfetch": "^3.0.0",
"next": "^9.3.0",
"next-compose-plugins": "^2.2.0",
"react": "^16.12.0",
"react-bootstrap": "^1.0.0-beta.17",
"react-dom": "^16.12.0",
"react-optimize": "^2.2.1",
"sass": "^1.26.2"
}
}
Also, I’m using ZEIT Now, therefore in dev using:
now dev
Thank you for your help!
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Reactions: 13
- Comments: 25 (8 by maintainers)
If you turn on next-transpile-modules https://www.npmjs.com/package/next-transpile-modules this error will go away.
EDIT: In case people come here wondering why people need this; at the moment i would say it serves 2 groups of people
Group 1 are running a monorepo and therefore they want to be able to import they’re other packages from node_modules.
Group 2 are bundling an external UI library except instead of producing a single index.css like you’re used to they are instead leaving the “.module.scss” imports in the output artifact so when people import that component they automatically only import the critical css not ALL the css always.
Have the same issue without using
next-transpile-moduleat all. So do I need to install and configure it to fix this?This is happening to me too, the cause is the dynamic import. If i have a dynamic import like import(“…/components/Foo”) everything is ok, but if the import is import(`…/components/${foo}`) the warning appears.
Everything seems to be working properly, but the warning is annoying because you will get one warning for each component inside the folder.
I’m still struggling with this issue, I’m using next 10.0.0
I tried to use
next-transpile-modulebut warnings still appears, I just created a.module.scssfile in mysrc/componentsfolder, no imported it like @Danetag said.Can someone help us ? and explain how
next-transpile-modulecan resolve this issue ?@Timer Why did you close this issue ? It’s definitively a Next.js issue while I’m not using
next-transpile-module😃Is it possible to re-open it ? Thx !
Thanks !
I’m getting this after upgrade to Next.js 9.5. Exact same codebase worked fine with 9.4.x.
Note: you must be using at least v3.1.0 of next-transpile-modules for it to support transpiling CSS from node_modules: https://github.com/martpie/next-transpile-modules/releases/tag/3.1.0
I think it’s a problem with next-transpile-modules. Here is the issue: https://github.com/martpie/next-transpile-modules/issues/95
@timneutkens What do you mean exactly? You want a component example? This warning is triggered without having to import the file, just by creating it.
Is there anything else I could provide? Thanks!
Closing as this was a bug with
next-transpile-moduleand not related to Next.js. Please upgrade to v4.0.2 or newer!