webpack
Sass loader forThis is a fork.
I forked sass-loader
and left in most of the code for now - but I am planning to change this code so it will work with the SassPort module. My goal is to keep API compatibility and have this module pass the same tests as the original sass-loader
, just that this one has more features.
Install
npm install sassport-loader --save
The sass/sassport-loader requires node-sass or SassPort and webpack.
Usage
var css = ;// => returns compiled css code from file.scss, resolves importsvar css = ;// => returns compiled css code from file.scss, resolves imports and url(...)s
Use in tandem with the style-loader
and css-loader
to add the css rules to your document:
;
NOTE: If you encounter module errors complaining about a missing style
or css
module, make sure you have installed all required loaders via npm.
Apply via webpack config
It's recommended to adjust your webpack.config
so style!css!sass!
is applied automatically on all files ending on .scss
:
moduleexports =module:loaders:test: /\.scss$/loaders: "style" "css" "sassport";
Then you only need to write: require("./file.scss")
.
SassPort modules and options
In order to pass additional things to the SassPort .render()
function, use the SassPort entry within your config:
moduleexports =module:loaders:test: /\.scss$/loaders: "style" "css" "sassport"Sassport:modules:// These modules will be passed to SassPortoutputStyle: "compressed"// ... and more ...;
See node-sass for all available options. Just note that SassPort might not support all and every option.
Imports
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 ~
which tells webpack to look-up the modulesDirectories
.
;
It's important to only prepend it with ~
, because ~/
resolves to the home-directory. webpack needs to distinguish between bootstrap
and ~bootstrap
because CSS- and Sass-files have no special syntax for importing relative files. Writing @import "file"
is the same as @import "./file";
.sass files
For requiring .sass
files, add indentedSyntax
as a loader option:
moduleexports =module:loaders:test: /\.sass$/// Passing indentedSyntax query param to node-sassloaders: "style" "css" "sassport"Sassport:indentedSyntax: true;
url(...)
Problems with Since Sass/libsass does not provide url rewriting, all linked assets must be relative to the output.
- 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.
main.scss
).
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.
Source maps
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" "sassport" Sassport: sourcemap: true ;
If you want to edit the original Sass files inside Chrome, there's a good blog post. Checkout test/sourceMap for a running example.
License
MIT (http://www.opensource.org/licenses/mit-license.php)
Reminder
This is a fork. The code is likely to change since I am migrating it to use Sassport instead. Feel free to explore the code, though! :)
Fork is by: Ingwie Phoenix