@jwalsh/eslint-config-esnext

1.6.2 • Public • Published

Pluggable ESLint config for ECMAScript Next that you can import, extend and override

Join the chat at https://gitter.im/kunalgolani/eslint-config npm version npm downloads GitHub issues Deps Dev Deps

ESNext: Safety Checks and Best Practices with a bias toward code concision / brevity

Usage

In your js project directory:

npm install --save-dev eslint-config-esnext

And in your .eslintrc.yaml:

---
  extends:
    - esnext

Alternatively, in your .eslintrc.js or .eslintrc.json:

{
  "extends": ["esnext"]
}

To add a git-hook to your commits, consider using husky

npm install --save-dev husky

And in your package.json:

  "scripts": {
    "precommit": "eslint ."
  }

Config

This config is biased and opinionated, and errs on the side of too many rules instead of too few. Think of this as a superset of your repo's lint config, and discard what you don't like in it. It's easy to override and disable the rules you find inconvenient.

  env:
    es6: true
    commonjs: true

enables ES6 features and CommonJS modules

  parser: babel-eslint

enables parsing all babel supported code

  parserOptions:
    ecmaVersion: 7
    sourceType: module
    ecmaFeatures:
      impliedStrict: true
      modules: true
      experimentalObjectRestSpread: true

allows es2015 modules and es2016 object rest and spread to be parsed, and applies strict mode to all js code

  extends:
    - eslint:recommended
    - plugin:import/errors
    - plugin:import/warnings

includes the following rules:

  rules:

selected from here, configured to:


ESNext Style Guide

Package Sidebar

Install

npm i @jwalsh/eslint-config-esnext

Weekly Downloads

0

Version

1.6.2

License

ISC

Last publish

Collaborators

  • jwalsh