Possibility to pass options to css-loader and sass-loader when using (s)css modules
See original GitHub issueFeature request
Is your feature request related to a problem? Please describe.
I’d like to pass further options (like includePaths
or localIdentName
) to sass-loader/css-loader when using the new built in css modules.
Additional context
Maybe hashing the css classnames via localIdentName: [hash:base64]
in production mode could be a default.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:18
- Comments:5 (3 by maintainers)
Top Results From Across the Web
sass-loader - webpack - JS.ORG
To enable CSS source maps, you'll need to pass the sourceMap option to the sass-loader and the css-loader. webpack.config.js module.exports = { devtool:...
Read more >sass-loader
Loads a SASS/SCSS file and compiles it to CSS. Use the css-loader or the raw-loader to turn it into a JS module and...
Read more >How to configure SCSS modules for Webpack
First, SCSS is converted to CSS ( sass-loader ), then run through css-loader to process @import() , url() etc, then style-loader (to be...
Read more >How do I pass options to SASS loader for style within .vue files?
You can pass it as includePaths which is a sass option like following: module.exports = { ... module: { loaders: [ { test:...
Read more >Setting up CSS and Sass with Webpack!! - DEV Community
scss, etc we need the help of loaders to compile it. Let see how to do it. Setting up CSS with webpack. At...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I would go with A) since people might be used to it from the old next-plugins, e.g. https://github.com/zeit/next-plugins/blob/master/packages/next-sass/readme.md
Something like:
As a workaround for now, you can do the following to get your custom options in there. It’s not pretty but it works…