Skip to content
Personal ESLint configuration
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.editorconfig
.eslintrc
.gitignore
CHANGELOG.md
LICENSE
README.md
index.js
index.yml
package.json

README.md

eslint-config-bgw

This is a sharable config for ESLint to allow me to keep a consistent linter configuration between my personal projects.

It's based on, but diverges from Facebook's ESLint configuration, which I helped develop. Mostly, it's stricter.

Adding to a project

$ npm i --save-dev eslint eslint-config-bgw
$ echo 'extends: bgw' >> .eslintrc

Notes on SemVer

This project will follow Semantic Versioning. To quote the specification:

  1. MAJOR version when you make incompatible API changes,
  2. MINOR version when you add functionality in a backwards-compatible manner, and
  3. PATCH version when you make backwards-compatible bug fixes.

Because tightening the configuration (and therefore disallowing code that was previously valid) is potentially breaking, except in the case of warnings, I will increment the MAJOR version every time I tighten the configuration. If I loosen the configuration, I'll increment the MINOR version.

This means that I expect the version number to grow quickly. Version numbers say nothing about the maturity of a project.

You can’t perform that action at this time.