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

pour-css

v1.3.1

Published

Pour is a minimalist CSS bundler (~100 LOC). It leaves your CSS files completely alone except for one rule:

Downloads

17

Readme

pour-css

Pour is a minimalist CSS bundler (~100 LOC). It leaves your CSS files completely alone except for one rule:

@import (inline) "./my-file.css"

Upon seeing this syntactically-invalid rule, Pour will resolve, read, and inline the contents of that file in place of the rule.

Pour does not minify or process your CSS in any way – there are already dedicated tools for that. Pour does one thing and it does it well.

But why?

You might not need SASS (common installation problems), LESS (poor tooling), or PostCSS (complex setup). CSS has become quite mature out-of-the-box. Did you know browsers now widely support...

Usage

yarn install pour-css
# or
npm install pour-css

You can use Pour via the command line or its JavaScript API.

Command Line Interface (CLI)

pour my/style.css > bundle.css

JavaScript API

Pour exposes a bundle function that takes a file path and returns a stream.

var Pour = require('pour-css');

You can pipe to a file...

Pour.bundle(__dirname + '/css/index.css')
    .pipe(fs.createWriteStream('bundle.css'));

...or pipe to a HTTP response!

var http = require('http')

http.createServer((req, res) => {
  if ( req.method === 'GET' && req.url === '/style.css' ) {
    Pour.bundle(__dirname + '/css/index.css')
        .pipe(res);
  }
  // ...
});

Caveats

If you're mixing @import and @import (inline), be careful about how you order them. According to the official CSS spec, all @import rules must precede all other rules in your stylesheet. In practice, any @import rule that doesn't follow the spec is ignored by the browser.

What does this mean for you? Just use these two rules of thumb and you should be good:

  1. Don't @import (inline) a file that contains normal @import statements (or be very careful about it)
  2. Put all @import (inline) statements after your normal @import statements (if you have any).

Testing

If you're adding a feature or fixing a bug, clone this repo down, npm install, and use the following to run the test suite:

npm test