eslint-config-rp

This package provides shareable ESLint configurations for JavaScript projects that conform with Renaissance Periodization's coding style.

Installation

To make use of this config, install ESLint (>= 2.0) and this package as a development dependency of your project:

npm install eslint eslint-config-rp --save-dev

Next, add an eslintConfig member to your project's package.json. At a minimum, this config file must include an extends member:

{
  "eslintConfig": {
    "extends": "rp"
  }
}

See the ESLint configuration guide for details on additional configuration options. Any rules configured in your package.json file will override those provided by the eslint-config-rp package.

Use

You should run the linter as part of (or before) your tests. Assuming tests are run before any proposed changes are merged, this will ensure coding standards are maintained in your default branch. Using npm scripts is the preferred way to run the linter without requiring it to be a global dependency. Assuming you want to lint all JavaScript files in your project, add the following entry to your package.json:

{
  "scripts": {
    "pretest": "eslint src"
  }
}

With this pretest entry in your package.json, ESLint will run on all JavaScript files in the src directory of your project using your .eslintrc config when tests are run:

npm test

See the ESLint CLI guide for additional options when running ESLint.

In addition to running the linter when your tests are run, you should configure your editor to run the linter as well. See the ESLint integration page to find details on configuring your editor to warn you of ESLint errors.

See the examples directory for more usage examples.

Profiles

The eslint-config-rp package includes a number of ESLint configuration profiles for different types of projects.

rp (base config)

The "base" config is suitable for Node projects or browser-based projects using a CommonJS module loader (e.g. Browserify or Webpack).

Example configuration in package.json:

{
  "eslintConfig": {
    "extends": "rp"
  }
}

rp/react

The rp/react config is suitable for projects using React. This extends the base config to include the React plugin, enable JSX parsing, and run React specific rules. To use this profile, you'll need to install the eslint-plugin-react package:

npm install eslint-plugin-react --save-dev

Then your minimal configuration in package.json would look like this:

{
  "eslintConfig": {
    "extends": "rp/react"
  }
}

Development

To add another configuration profile, add a new config script to the root of the repository directory (e.g. new-config.js). This script should export an ESLint config object and should have an extends: './index.js' property. People using this config will add extends/new-config to their own ESLint config.

You should add and example for your new profile and ensure that tests pass with any changes.

npm test

After adding a new config profile or modifying an existing one, publish a new version of the package. Adding a new "error" level rule constitutes a major release. A new profile or non-breaking modification to an existing profile (e.g. a "warning" level rule) can be a minor release.

Publishing a new minor release would look like this:

# commit and push any changes first
npm version minor # this bumps the package.json version number and tags
git push --tags origin master
npm publish

License

© 2018 Renaissance Periodization, LLC.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.