Package Exports
- metalsmith-sass
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (metalsmith-sass) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
metalsmith-sass
A Sass plugin for Metalsmith.
Installation
npm install --save metalsmith-sassGetting Started
If you haven't checked out Metalsmith before, head over to their website and check out the documentation.
CLI Usage
If you are using the command-line version of Metalsmith, you can install via npm, and then add the
metalsmith-sass key to your metalsmith.json file:
{
"plugins": {
"metalsmith-sass": {
"outputStyle": "expanded"
}
}
}JavaScript API
If you are using the JS Api for Metalsmith, then you can require the module and add it to your
.use() directives:
var sass = require('metalsmith-sass');
metalsmith.use(sass({
outputStyle: "expanded"
}));Options
See node-sass for a complete list of supported options.
In addition to the options that node-sass provides, metalsmith-sass provides the following options:
outputDir
Change the base folder path styles are outputed to. You can use this in combination with
Metalsmith's destination option to control where styles end up after the build.
The final output directory is equal to Metalsmith.destination() + outputDirOption. For example,
the following setup output styles to build/css/ even though the source files are in src/scss/:
Metalsmith()
.source("src/")
.destination("build/")
.use(sass({
outputDir: 'css/' // This changes the output dir to "build/css/" instead of "build/scss/"
}))
.build(function () {
done();
});Source Maps
The easiest way to enable source maps in your metalsmith project is to add the following options:
Metalsmith()
.source("src/")
.destination("build/")
.use(sass({
sourceMap: true,
sourceMapContents: true // This will embed all the Sass contents in your source maps.
}))
.build(function () {
done();
});Though the sourceMapContents is not required, I recommend adding it, otherwise you'll need to
manually serve up your .scss files along with your compiled .css files when you publish your
site.
Credits
Thanks to Segment.io for creating and open-sourcing Metalsmith! Also thanks to the whole community behind the node-sass project.