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

eslint-config-lob

v6.0.0

Published

Shareable ESLint config for Lob repositories

Downloads

12,267

Readme

eslint-config-lob

Shareable ESLint configuration for Lob repositories

Usage

  1. Install eslint and this module:
npm i eslint eslint-config-lob --save-dev
  1. Create an .eslintrc file in the root of your project with the following object:
{
  extends: "eslint-config-lob"
}

This will use the rules in eslint-config-lob's index.js. You can access rules in files other than eslint-config-lob's index.js via:

{
  extends: "eslint-config-lob/migrations"
}
  1. Use an .eslintignore file to specify files or directories that the linter should ignore. By default, eslint ignores the node_modules directory.
  2. Modify or create the npm lint script in the package.json to:
{
  "scripts": {
    "lint": "eslint ."
  }
}

This will lint every .js file in your project.

  1. Clean up any old lint or style tasks and config from your project.
  2. Don't forget to shrinkwrap before you commit your changes.

Contributing

Modifying or adding rules.

  • To add to the main rules, modify the index.js file.
  • To use most of the main rules but override some of them, create a new file in the root of this module, extend from index.js and add your overrides. See migrations.js for an example. If you're creating a file like this, its rules should be reusable and not a one-off. For example, you could create a file for angular rules. To make a one-off change, do so in your project's .eslintrc.