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

postcss-scss-node-sass-importer

v1.0.4

Published

PostCSS plugin to resolve imports with a node-sass importer plugin

Downloads

4

Readme

postcss-scss-node-sass-importer

PostCSS plugin to resolve and inline @import statements using a node-sass importer instance.

Why not postcss-import? postcss-import follows the css @import spec, not the sass @import spec, which can lead to errors or unpredicted results when parsing scss files.

By using a node-sass importer to resolve imports, you can use the exact same import process as your scss compiler.

Notes

  • Like the postcss-import plugin, you will want to apply this plugin as early as possible in the chain so you can treat the output as a single scss string.
  • Like the postcss-import plugin, duplicates will only be inlined once, at the highest point they occur.
  • Unline the postcss-import plugin, this plugin does not follow the css @import spec.

Installation

With yarn

$ yarn add postcss-scss-node-sass-importer

Or npm:

$ npm install --save postcss-scss-node-sass-importer

Usage

const fs = require('fs'),
	postcss = require('postcss'),
	syntax = require('postcss-scss'),
	importer = require('postcss-scss-node-sass-importer')
	
const scss = fs.readFileSync('scss/input.scss', 'utf-8')
	
postcss(importer()).process(scss, {
  syntax: syntax,
  from: 'scss/input.scss',
})

scss/input.scss:

@import 'npm-package'

Will give you:

... The expanded npm package scss

Options


opts.importer

The node-sass importer plugin to use.

See the npm-sass importer.

Default:

require('npm-sass').importer


opts.resolver

Takes the output from the node-sass importer and resolves it to a file on the file system.

See the default resolver.

Default:

require('./lib/default-resolver')


opts.fixBroken

Removes unresolvable @import statements instead of triggering an error.

Default:

false


opts.filter

A function that allows you to filter which @import statements get inlined.

<bool> [async] filter(<String> sourcepath, <String> importpath, <string> targetpath)
  • sourcepath is the path to the file that has the @import statement.
  • importpath is the contents of the @import statement.
  • targetpath is the resolved local filesystem path.

The function should return true to inline the import, false otherwise.


opts.plugins

A list of postcss plugins to apply on imported content. This usually should not be necessary. You typically want to apply plugins at the root level after inlining has already happened.

For more information see the scss-extractor documentation.