webpack-fix-style-only-entries VS css-loader

webpack-fix-style-only-entries for Webpack 4

@fbem/css-loader is very similar to css-loader (and actually a fork of it) and has almost the same set of options and functionality. You can even use it with different style preprocessors by simply chaining loaders together in webpack config. But be sure to pick up if you need them 😏.

Css files need a css loader like https://github.com/webpack-contrib/css-loader. In fact I see you already have 2 css loaders in your normal webpack config. the server config needs those too. Your fronted build and server build will be very similar in that regard.

React comes by default with css module support via https://github.com/webpack-contrib/css-loader, which is stable and not deprecated. (Note that this entirely independent of react)

I have enabled CSS modules within webpack.config in my React application so that I can locally scope CSS files to individual components. I'm also trying to use the TabView component from PrimeReact. When I do so the themes from PrimeReact are not applied. If I create a separate project and do not enable CSS modules the themes apply correctly.

this is technically a feature of css-loader and not of nextjs, next just supports it ootb through their webpack config. iirc its this option you need to customize

const config = { mode: isProdBuild ? 'production' : 'development', devtool: isProdBuild ? 'source-map' : 'cheap-module-eval-source-map', entry: { app: `${SRC_DIR}/index.js`, }, optimization: { minimize: isProdBuild, sideEffects: true, }, context: SRC_DIR, stats: { colors: true, hash: true, timings: true, assets: true, chunks: false, chunkModules: false, modules: false, children: false, warnings: true, }, module: { rules: [ transpileJavaScriptRule(mode), loadWebWorkersRule, loadShadersRule, ], }, resolve: { // Which directories to search when resolving modules modules: [ // Modules specific to this package path.resolve(__dirname, '../node_modules'), // Hoisted Yarn Workspace Modules path.resolve(__dirname, '../../../node_modules'), SRC_DIR, ], // Attempt to resolve these extensions in order. extensions: ['.js', '.jsx', '.json', '*'], // symlinked resources are resolved to their real path, not their symlinked location symlinks: true, }, plugins: [ new webpack.DefinePlugin({ /* Application */ 'process.env.NODE_ENV': JSON.stringify(process.env.NODE_ENV), 'process.env.DEBUG': JSON.stringify(process.env.DEBUG), 'process.env.APP_CONFIG': JSON.stringify(process.env.APP_CONFIG || ''), 'process.env.PUBLIC_URL': JSON.stringify(process.env.PUBLIC_URL || ''), 'process.env.VERSION_NUMBER': JSON.stringify(PACKAGE.version || ''), 'process.env.BUILD_NUM': JSON.stringify(BUILD_NUM), /* i18n */ 'process.env.USE_LOCIZE': JSON.stringify(process.env.USE_LOCIZE || ''), 'process.env.LOCIZE_PROJECTID': JSON.stringify(process.env.LOCIZE_PROJECTID || ''), 'process.env.LOCIZE_API_KEY': JSON.stringify(process.env.LOCIZE_API_KEY || ''), /* XNAT dev */ 'process.env.XNAT_PROXY': JSON.stringify(process.env.XNAT_PROXY || ''), 'process.env.XNAT_DOMAIN': JSON.stringify(process.env.XNAT_DOMAIN || ''), 'process.env.XNAT_USERNAME': JSON.stringify(process.env.XNAT_USERNAME || ''), 'process.env.XNAT_PASSWORD': JSON.stringify(process.env.XNAT_PASSWORD || ''), }), ], // // Fix: https://github.com/webpack-contrib/css-loader/issues/447#issuecomment-285598881 // // For issue in cornerstone-wado-image-loader // node: { // fs: 'empty', // }, };

One possible non-JSS solution is css-modules supported in css-loader. That requires some setup which may get convoluted if you need CSS preprocessors or SSR.

✨ css loader 💥 jss 🌟 csjs ☄️ aphrodite

Before we start, you should have a minimum knowledge of webpack, you should have css-loader. Along this article, I use nuxt for example, but you can use React or Angular.

The above should work in Create React App out of the box. If you are rolling your own Webpack configuration (may God have mercy on your soul), you'll need to configure modules with a compileType of icss: