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 🙏

© 2026 – Pkg Stats / Ryan Hefner

grunt-css-versioning

v0.1.0

Published

Enables to use several versions (forks) of component styles

Readme

CSS versioning plugin for grunt.

Description

This is just a beta version that was created as a prototype for some research.

Installation

To install it you can simply clone it to your project node modules.

Usage example

Here is the usage example.

The task works with several css files, which are named according to predefined rules (you can change it if you want). That files can look this way:

myComponent.css:

    myComponent {
        color: #3B3B3B;
    }

    myComponent a.link {
        border: 1px solid #333;
    }

myComponent--v2.css:

    .myComponent {
        color: #000;
    }

    .myComponent a.link {
        border: 1px solid #bbb;
    }

myComponent--v3.css:

    .myComponent {
        color: #3A2A1A;
    }

    .myComponent a.link {
        border: 4px solid #3b001F;
    }

Using the task you will have the following output:

    .myComponent {
        color: #3B3B3B;
    }

    .myComponent a.link {
        border: 1px solid #333;
    }

    .v2--myComponent {
        color: #000;
    }

    .v2--myComponent a.link {
        border: 1px solid #bbb;
    }

    .v3--myComponent {
        color: #3A2A1A;
    }

    .v3--myComponent a.link {
        border: 4px solid #3b001F;
    }

Unfortunately, right now the task can't merge css classes to avoid extra defenitions.

Options

separator

|Parameter|Value| | ------------- | ------- | |Name|separator| |Type|String| |Descriptions|Defines the way of splitting for component name and version. RegExp part.| |Default value|"--"|

N.B. Please use it carefully, because it is a part of regular expression.

mergeVersion

|Parameter|Value| | ------------- | ------- | |Name|mergeVersion| |Type|Boolean| |Descriptions|Defines if we are to write all versioned css rules into component file| |Default value|true|

N.B. This regExp is used to get array [fileName, componentName, versioningToken, extention] array. For example ["component--v2.css", "component", "v2", "css"] for component--v2.css file.

License

MIT