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

@density/nicss

v1.3.0

Published

(pronounced like `nice`)

Downloads

2

Readme

Nicss

(pronounced like nice)

Nicss is a css helper library that extracts exported stylesheets out of node_modules and symlinks them into a single styles/ folder. This makes it easier to include the stylesheets of dependencies with css post-processors.

How it works

As an unofficial standard, many popular packages are adding a style field to their package.json file that links to their compiled css. Nicss crawls through your dependency graph and finds packages with this style property and symlinks each compiled css file to a single styles/ folder.

Here's an example project:

.
├── node_modules
│   ├── one
│   │   ├── package.json         // contains `"style": "./one-styles.css"`
│   │   └── one-styles.css       // contains `.one { color: red; }`
│   └── two
│       ├── package.json         // contains `"style": "./two-styles.css"`
│       └── two-styles.css       // contains `.two { color: blue; }`
├── index.js
└── package.json

When you run nicss, this is what happens:

.
├── node_modules
│   ├── one
│   │   ├── package.json         // contains `"style": "./one-styles.css"`
│   │   └── one-styles.css       // contains `.one { color: red; }`
│   └── two
│       ├── package.json         // contains `"style": "./two-styles.css"`
│       └── two-styles.css       // contains `.two { color: blue; }`
├── index.js
├── package.json
└── styles // nicss creates this folder...
    ├── one.css -> ../node_modules/one/one-styles.css // ... and symlinks each package's stylesheet inside.
    └── two.css -> ../node_modules/two/two-styles.css

Now, any package's defined stylesheet is accessible from within one folder:

$ # ie, cat styles/$PACKAGENAME.css
$ cat styles/one.css
.one { color: red; }
$ cat styles/two.css
.one { color: two; }

This is a format that tools like node-sass (using includePaths) and less (using paths) can easily consume:

// node-sass
// Note: run `nicss --ext scss` to output scss instead of css files for the below to work.
const sass = require('node-sass');
sass.render({
  data: '@import "one";',
  includePaths: ['./styles'],
}, function(err, output) {
  console.log(err, output)
});

// less
const less = require('less');
less.render('@import "one.css";', {
  paths: ['./styles']
}, function (e, output) {
  console.log(err, output);
});

How to use

  1. Install Nicss: npm i -S @density/nicss
  2. Give it a try manually first: run ./node_modules/.bin/nicss
  3. Add a postinstall hook to your package, so that after running npm install, css dependencies are linked for you: "postinstall": "nicss"
  4. Done. CSS dependencies will be automatically extracted when you run npm install.

Why not webpack?

Webpack is magic. Magic can be great when it works, but can be confusing and complicated. We've opted to minimize our use of webpack so that we have a deep understanding of our build process.