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

@neozenith/eslint-config

v3.0.0

Published

Shareable esLint config

Downloads

3

Readme

ESLint Config

Shareable ESLint Configuration to apply coding standards across javascript development.


Getting Started

Installation

Install peer dependencies and install the eslint configuration:

npm install --save-dev eslint prettier eslint-plugin-prettier eslint-config-prettier
npm install --save-dev @neozenith/eslint-config
echo "**/node_modules/**" >> .eslintignore

Configuration

Basic Configuration

Then add the following to your package.json:

{
  "eslintConfig":{ "extends": "@neozenith" }
}

Well that seems really simple right? And everyone gets the same rules, no excuses.

Advanced Configuration

In future, environment specific rules, would be specified as below:

  "eslintConfig":{
    "extends":[
      "@neozenith",
      "@neozenith/eslint-config/node"
    ]
  }
}

Scripts

Finally you'll want to add the following scripts to your package.json.

{

  "scripts": {
    "test:lint:all":"./node_modules/.bin/eslint --ignore-path .",
    "test:lint":"npm run test:lint -- --quiet",
    "test:lint:fix":"npm run test:lint -- --fix",
    "pretest":"npm run test:lint"
  }
}
  • test:lint:all - this will run eslint as per usual outputting all errors and warnings
  • test:lint - including the --quiet flag reduces eslint's output to errors only
  • test:lint:fix - this fixes all errors that are auto-fixable such as formatting issues that do not impact the semantics of the code. All prettier rules are always auto-fixable.
  • pretest - By running this before your tests it will enforce linting and halt on any errors preventing npm test from actually running until linting is satisfied. You may want to update this to test:lint:all so that it breaks on warnings too.

Maintaining

# Bump version number according to changes
npm version [major|minor|patch]

# Publish a public scoped repository
npm publish