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 🙏

© 2025 – Pkg Stats / Ryan Hefner

build-lint

v2.0.8

Published

Linting command line tool.

Readme

build-lint

This tool is currently in BETA

Overview

This is a command line tool that performs linting. It uses eslint to perform linting and includes the eslint-config-iservices package which defines the linting rules to be applied.

Guide

To install this tool execute the following npm console command from within your project.

npm install --save-dev build-lint

When the package is installed it will create a new .eslintrc file within the root of your project if one doesn't exist already. This file is required and can be modified to fine tune the linting rules that will be applied to your project. See the eslint configuration documentation for details about configuration options.

Once the package is installed you can run the tool from a terminal using the build-lint command. Normally you will do this within an npm script element. Take the following excerpt from an example package.json file:

{
  "scripts": {
    "lint": "build-lint \"src/**/*.js\" \"!src/tests/**/*.js\"",
    "lint-watch": "build-lint \"src/**/*.js\" \"!src/tests/**/*.js\" -w",
  }
}

In the example above the lint script will perform linting on files with an extension of .js within the src folder but not within the src/tests folder. The lint-watch script will perform linting on the same files whenever one of them is updated or added.

Also notice that the glob patterns are surrounded by double quotes. This is necessary in order to prevent the terminal from expanding the glob patterns into actual file paths.

API

Usage:

build-lint <files> [<files>] [-w]

Options:

| Option | Description | | --- | --- | | <files> | A glob pattern that identifies files to lint. Multiple glob patterns can be specified. | | -w | When present the files specified in the glob pattern(s) will be watched for changes and linted when they do change. |