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

node-sass-importer

v2.0.2

Published

Implementation of custom importer for node-sass

Downloads

1,634

Readme

node-sass-importer

Simple implementation of custom importer of SCSS files for node-sass. May be useful in a case if your SASS styles includes some third-party libraries and you don't want to hard link paths to them into your code.

Also it mimics compass-import-once functionaliy and avoid repetitive loading of SCSS files that are included multiple times into project.

Usage

Example usage in Gulp task

gulp.src('*.scss')
    .pipe(sass({
        importer: require('node-sass-importer')
    })

Options

Since importer signature is defined by node-sass itself - additional options are stored into importerOptions entry within node-sass options set. Importer tries to locate SCSS files by constructing their paths from given parts. They are:

roots

Array of additional root paths to search for SCSS files in. Should be defined as relative paths against current directory, main Node process is running from.
Default: ['']

paths

Array of additional path components within any of root paths to search SCSS files in. Can contain {url} placeholder, it will be replaced with value of url argument that is passed to importer.
Default: ['', '{url}']

filePrefixes

Array of prefixes to set before SCSS file name. Normally is not need to be overridden.
Default: ['_', '']

fileExtensions

Array of file extension to set after SCSS file name. Normally is not need to be overridden.
Default: ['.scss', '/_index.scss']

Importing of third-party libraries

Since v2.0 in a case if you're importing third-party library from node_modules - you can do it by use ~ as a prefix.

For example: @import "~bootstrap/scss/bootstrap".

Import of directory index files

Since v2.0 you can load some-dir/_index.scss by simply referencing directory itself: @import "some-dir"