npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

metalsmith-sass

v2.0.0

Published

Sass plugin for Metalsmith.

Downloads

2,319

Readme

metalsmith-sass

Build Status

A Sass plugin for Metalsmith.

Installation

npm install --save metalsmith-sass node-sass

Note: As of v2.0, node-sass is listed as a peer dependency, and will need to be installed alongside metalsmith-sass as shown above.

Getting 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 output 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();
  });

As of version v1.1, you can also use a function to dynamically manipulate the output dir.

This is useful if you want to preserve your folder structure, but change just one folder name.

Metalsmith(__dirname)
  .source("src/")
  .destination("build/")
  .use(sass({
    outputDir: function(originalPath) {
      // this will change scss/some/path to css/some/path
      return originalPath.replace("scss", "css");
    }
  }))
  .build(function () {
    done();
  });

Source Maps

The easiest way to enable source maps in your metalsmith project is to add the following options:

Metalsmith(__dirname)
  .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.

.sass files

As of version v1.2, metalsmith-sass automatically handles .sass files, so you don't need to specify the indentedSyntax option. Though you might still need set options for indentType and indentWidth if you are using something other than 2 spaces for indentation.

Credits

Thanks to Segment.io for creating and open-sourcing Metalsmith! Also thanks to the whole community behind the node-sass project.