npm install sass-loader node-sass webpack --save-dev
var css = ;// returns compiled css code from file.scss, resolves Sass importsvar css = ;// returns compiled css code from file.scss, resolves Sass and CSS imports and url(...)s
Please note: If you encounter module errors complaining about a missing
css module, make sure you have installed all required loaders via npm.
Apply via webpack config
It's recommended to adjust your
style!css!sass! is applied automatically on all files ending on
moduleexports =...module:loaders:test: /\.scss$/loaders: "style" "css" "sass";
Then you only need to write:
You can pass options to node-sass by defining a
sassLoader-property on your
webpack.config.js. See node-sass for all available Sass-options.
moduleexports =...module:loaders:test: /\.scss$/loaders: "style" "css" "sass"sassLoader:includePaths: path;
Passing your options as query parameters is also supported, but can get confusing if you need to set a lot of options.
If you need to define two different loader configs, you can also change the config's property name via
moduleexports =...module:loaders:test: /\.scss$/loaders: "style" "css" "sass?config=otherSassLoaderConfig"otherSassLoaderConfig:...;
webpack provides an advanced mechanism to resolve files. The sass-loader uses node-sass' custom importer feature to pass all queries to the webpack resolving engine. Thus you can import your Sass modules from
node_modules. Just prepend them with a
~ to tell webpack that this is not a relative import:
Alternatively, for bootstrap-sass:
It's important to only prepend it with
~/ resolves to the home directory. webpack needs to distinguish between
~bootstrap because CSS- and Sass-files have no special syntax for importing relative files. Writing
@import "file" is the same as
If you want to prepend Sass code before the actual entry file, you can simply set the
data-option. In this case, the sass-loader will not override the
data-option but just append the entry's content. This is especially useful when some of your Sass variables depend on the environment:
moduleexports =...sassLoader:data: "$env: " + processenvNODE_ENV + ";";
- If you're just generating CSS without passing it to the css-loader, it must be relative to your web root.
- If you pass the generated CSS on to the css-loader, all urls must be relative to the entry-file (e.g.
More likely you will be disrupted by this second issue. It is natural to expect relative references to be resolved against the
.scss-file in which they are specified (like in regular
.css-files). Thankfully there are a two solutions to this problem:
- Add the missing url rewriting using the resolve-url-loader. Place it directly after the sass-loader in the loader chain.
- Library authors usually provide a variable to modify the asset path. bootstrap-sass for example has an
$icon-font-path. Check out this working bootstrap example.
Bundling CSS with webpack has some nice advantages like referencing images and fonts with hashed urls or hot module replacement in development. In production, on the other hand, it's not a good idea to apply your stylesheets depending on JS execution. Rendering may be delayed or even a FOUC might be visible. Thus it's often still better to have them as separate files in your final production build.
There are two possibilties to extract a stylesheet from the bundle:
- extract-loader (simpler, but specialized on the css-loader's output)
- extract-text-webpack-plugin (more complex, but works in all use-cases)
To enable CSS Source maps, you'll need to pass the
sourceMap-option to the sass- and the css-loader. Your
webpack.config.js should look like this:
moduleexports =...devtool: "source-map" // or "inline-source-map"module:loaders:test: /\.scss$/loaders: "style" "css?sourceMap" "sass?sourceMap";