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

css-band-aid

v4.2.4

Published

CSS Post-Processor

Downloads

7

Readme

css-band-aid NPM version build status Dependencies Join the chat at https://gitter.im/css-band-aid/css-band-aid

This is a fork of Bless.

Sometimes we can't get away from supporting Internet Explorer 9 and below. Unfortunately, this support can sometimes break our css due to these limitations, and when it does break it is almost impossible to track down. How do you get around such a crippling limitation? Well, you can slap this css-band-aid on top of your css and you should be alright.

css-band-aid analyzes your css files' selector counts and splits them appropriately, bringing them under the Internet Explorer's selector limit.

Installation

To use the cli tools:

npm install -g css-band-aid

To use the public api as part of your package:

npm install css-band-aid

CLI Usage

Commands:
  count   checks an existing css file and fails if the selector count exceeds IE limits
  chunk   breaks up css file into multiple files if it exceeds IE selector limits

Examples:
  bandaid count <file|directory>
  bandaid count <file|directory> --no-color
  bandaid chunk <file|directory>  (chunked files will reside next to input css files with the format *.##.css)
  bandaid chunk <file|directory> --out-dir <output directory>
  bandaid chunk <file|directory> --sourcemaps (write out sourcemaps for css files with the format *.##.css.map)

API Usage

chunk(cssString, [options])

Separate the cssString into chunks that can be used by IE.

options:
  source         the path to the file containing the provided css.
  sourceMaps     a boolean for whether or not to output sourcemaps. source must be provided (defaults to false)

returns:
  data                    An array of css strings for each css chunk
  maps                    An array of css sourcemap strings for each css chunk. This will be empty if source is not provided or sourcemaps is not enabled
  totalSelectorCount      The total number of selectors in the provided css

example:
  var parsedData = chunk(code, { source: './path/to/css.css' });
  parsedCss.data                  //An array of css strings for each css chunk
  parsedCss.maps                  //An array of css sourcemap strings for each css chunk. This is empty if source is empty or sourcemaps is false.
  parsedCss.totalSelectorCount    //The total number of selectors in the provided css file

chunkFile(filepath, options)

Separates the provided file into chunks.

options:
  sourcemaps      A boolean for whether or not to output sourcemaps. (Defaults to false)

returns:
  A promise object resolving the chunked data with the same properties as chunk()

example:
  chunkfile('./path/to/css.css').then(function(parsedCss, { sourcemaps: true }) {
    parsedCss.data                  //An array of css strings for each css chunk
    parsedCss.maps                  //An array of css sourcemap strings for each css chunk. This will be empty if sourcemaps is false.
    parsedCss.totalSelectorCount    //The total number of selectors in the provided css file
  });

License

See LICENSE file.

Copyright (c) Paul Young

Copyright (c) Css-Band-Aid