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

cssnow

v2.3.0

Published

Sort of like cssnext used to be

Downloads

22

Readme

cssnow

CircleCI

A CSS pre-processor, really simple to set up, sort of like cssnext used to be.

Back when we were young, cssnext used to be pretty simple: you installed it, you ran it, it worked. Nowadays, cssnext has evolved to build atop PostCSS, with lots of configuration coming with.

I have nothing against that move. It's a lot more powerful and flexible, and overall I think it is absolutely the right thing to do. But we have lots of repos, and they all need a default that's pretty much what cssnext used to be. So what cssnow does is pretty much that: use cssnext and PostCSS with a default setup that matches what we need. It's a whole lot fewer direct dependencies to worry about, and a way to centralise options we like (such as being safe out of the box when minifying).

This is for you if you like these defaults and don't want to think too much about your CSS pre-processing; if you prefer the flexibility and power stick to the full PostCSS stack!

Installation

The usual:

npm install --save cssnow

Usage

cssnow [options] <input> <output>

If output is unspecified, it prints to standard out; likewise if input is not specified it reads from standard in.

When NODE_ENV is set to production, it minifies and does not report errors; otherwise it does not minify but reports errors. Due to this behaviour, it (currently) produces no source maps.

Options include:

  • -w, --watch: enter watch mode

API

You can use cssnow as a library. It exports a single function (the default one). Call it with options and a callback. The options (all of which are optional) are:

  • watch: boolean, enter watch mode or not.
  • input: input path.
  • output: output path.

The callback will receive an error if there was one, just null otherwise.

It also has a few named exports: production, development, and configuration which are all the configuration objects for the respective environments plus the resolved one — these can be used with external tools that support a PostCSS configuration, such as webpack.

Global installation

You may install it globally if you wish to (with npm install -g cssnow), it will just work.