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-standard-deviation

v2.0.1

Published

a shared eslint-config for javascript ES5, ES2015, ES.next and React projects

Downloads

17

Readme

eslint-config-standard-deviation

npm version npm downloads bitHound Overall Score

ESLint shared configuration for javascript ES5, ES2015, ES.next and React projects based on standard shared eslint-config

What is different from standard eslint-config ?

standard shared eslint-config rules are almost fine but we do not like to force us to ...

  • not use semicolon ;
  • put space before function parens function foo ()

![eslint-config-standard-deviation][eslint-config-standard-deviation] [eslint-config-standard-deviation]:./semicolon.jpg

Installation

npm

npm install eslint-config-standard-deviation --save-dev

WITH dependencies

npm install eslint babel-eslint eslint-config-standard eslint-config-standard-react eslint-plugin-react eslint-plugin-promise eslint-plugin-standard --save-dev

OR add easily to projects using eslint-modules-standard-deviation

npm install eslint eslint-modules-standard-deviation --save-dev
Works only in npm 3 and beyond environments

Usage

Add extends to project .eslintrc

{
  "extends": ["standard-deviation"]
}

Add scripts to package.json

"scripts": {
  "lint": "eslint . --ext .js,.jsx",
  "testonly": "echo \"Error: no test specified\" && exit 1",
  "test": "npm run lint && npm run testonly"
}

[optional] enable/disable eslint rules

{
  "extends": ["standard-deviation"],
  "rules": {
    "space-before-function-paren": ["error", "always"]
  }
}

for Javascript ES5 only, use

Projects using eslint-config-standard-deviation

Contributing

  • Documentation improvement
  • Feel free to send any PR

License

ISC