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

piping-styles

v0.1.4

Published

Keep your styles piping hot! Rebuild your styles on change without binaries

Downloads

4

Readme

Piping-styles

Similar stuff to piping and piping-browser but for stylesheets. currently supports stylus with (optional) nib.

Installation

npm install piping-styles

Usage

Piping-styles is not a binary, so you can continue using your current workflow for running your application ("wooo!"). Basic usage is as follows:

require("piping-styles")({main:"./client/styles/app.styl",out:"./public/app.css"});

Options

  • main (path): The path to your top style
  • out (path): The path to where you want your css to be written to. Relative to the file where piping-styles was required
  • ignore (regex): Files/paths matching this regex will not be watched. Defaults to /(\/\.|~$)/
  • watch (boolean): Whether or not piping should rebuild on changes. Defaults to true, could be set to false for production
  • vendor (object): Specify configuration for building vendor files. Vendor files are concatenated in order, and written to the given path.
    • path (string): Directory where vendor files are located, relative to file where piping-styles was required
    • out (string): Path where vendor ouput should be written, relative to the file where piping-styles was required
    • files (array): Array of vendor files, relative to vendor path.
  • build (object): An object that maps file extensions, eg ".styl" to functions that take a filename, file data, and a callback and compile the source, sending it to the callback.

Piping-styles can also be used just by passing two strings. In this case, the strings are taken as the main and out options

require("piping-styles")("./client/styles/app.styl","./public/app.css");

piping-styles plays nice with piping. To use it, ensure piping-styles is required when piping returns false:

if(!require("piping")()){
  require("piping-styles")("./client/styles/app.styl","./public/app.css");
  return;
}
// application logic here