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-jameslnewell

v3.2.0

Published

ESLint config for common gotch'yas for different JS environments.

Downloads

82

Readme

eslint-config-jameslnewell

ESLint config for common gotch'yas for different JS environments.

Note: I think formatting code is important (find out why here) but nowdays I'm using prettier to take care of formatting code for me.

Installation

npm install --save eslint-config-jameslnewell

Usage

In the root of your project, create a .eslintrc file with the following contents:

{
  "extends": "jameslnewell/<env>"
}

Now run eslint on your script files:

eslint **/*.js

Configurations

jameslnewell/es5

Linting rules for ES5.

jameslnewell/es6

Linting rules for ES6.

jameslnewell/es

Linting rules for latest language features.

jameslnewell/react

Linting rules for ES6 and react.

jameslnewell/node

Linting rules for node v4.

Partial configurations

jameslnewell/test

Relax rules with useful behaviour for testing.

jameslnewell/debug

Relax rules with useful behaviour for debugging.

Change log

3.0.0-preview.*

  • break: removed all rules that enforced formatting
  • break: switch jameslnewell/test from mocha to jest
  • break: removed rules already configured in eslint:recommended

I bumped the major version because lots of people were using the preview.

2.0.0-preview.*

  • break: use webpack config for resolution of imports
  • break: moved mocha rules to the test configuration
  • break: turned on a whole heap of new import, reactandmocha` rules
  • break: using babel-eslint to support class properties

I bumped the major version because lots of people were using the preview.

1.0.0-preview.*

  • break: migrate to eslint v2

0.5.1

  • fix: moved eslint-plugin-mocha from devDependencies to dependencies

0.5.0

  • add: added eslint-plugin-mocha to prevent .only() slipping through