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-global-import-once

v1.0.2

Published

Import Sass files once globally.

Downloads

4

Readme

node-sass-global-import-once

Build Status

Import Sass files once globally.

Useful when you would want to exclude certain components in output files and leave them only in one location (e.g. one component is imported globally and any other attempt to load it would produce empty string). Goes along nicely with node-sass-import-once.

Installation

npm install node-sass-global-import-once --save

Usage

input/index.scss

@import "foo";
@import "bar";
@import "baz";

body {
	color:red;
}

input/page.scss

@import "foo";
@import "bar";
@import "baz";

body {
	color:red;
}
var sass = require('node-sass');
var gio = require('node-sass-global-import-once');

['./input/index.scss', './input/page.scss'].forEach(function ( file ) {

	sass.render({
		file: file,
		importer: [
			gio([
				{
					file: '**/index.scss',
					imports: [
						'foo',
						'baz'
					]
				}
			]),
		]
	}, function( err, result ) {
		//=> …
	});

});

Given two entry Sass files, they would be treated as:

input/index.scss

@import "foo";
@import "bar";
@import "baz";

body {
	color:red;
}

input/page.scss

@import "bar";

body {
	color:red;
}

page.scss doesn’t include foo and bar imports since they should be imported globally only once inside index.scss.

API

gio(definitions)

Package expects one argument, array of definitions (object) for global imports.

Each object definitions contains following properties:

file

Type: String

Name of the file or minimatch expression which is considered as global entry point.

imports

Type: Array

List of imports as strings which are considered to be global imports. Package only reads exact names defined inside files, so relative filenames which map to certain absolute package names are treated as different packages.

License

MIT © Ivan Nikolić