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

mocha-csslint

v2.0.0

Published

mocha-csslint -------- Run CSSLint as a Mocha test.

Downloads

31

Readme

mocha-csslint npm version Build Status

Run CSSLint as Mocha tests.

To install in your node.js project as devDependency, run this command, in the root of your project

npm install mocha-csslint --save-dev --save-exact

Usage

Mocha defaults to looking for your test specs in the test folder of your project. Add this file as test/csslint.spec.js in your project, with the following content:

require('mocha-csslint')('/client/static/css');

You should point to the place where you keep your css files instead of '/client/static/css' above.

That is it you are done.

You can still specify you csslint options in a .csslintrc file in the root of your project (see this project for an example)

To grep only the CSSLint test, just do

mocha --grep csslint

If you want to run CSSLint on several separate folders you can do:

require('mocha-csslint')(['/client/static/css', '/clinet2/css']);

Why?

This module was created to:

  • Make adding CSSLint testing to a project using Mocha as easy as possible
  • Make it easy to piggyback on all the different Mocha reporters (dot, spec, teamcity etc) for CSSLint output
  • Make sure that you get a click-able link directly to the problem in WebStorm, when CSSLint fails
  • Make sure that there is no unnecessary noise in the test output