eslint-config-dina

This package provides Digital Natives' .eslintrc as an extensible shared config.

Usage

We export three ESLint configurations for your usage.

eslint-config-dina

Our default export contains all of our ESLint rules, including ECMAScript 6+ and React. It requires eslint, eslint-plugin-import, eslint-plugin-react, and eslint-plugin-jsx-a11y. If you don't need React, see eslint-config-dina-base.

If you use yarn, run npm info "eslint-config-dina@latest" peerDependencies to list the peer dependencies and versions, then run yarn add --dev <dependency>@<version> for each listed peer dependency. See below for npm instructions.

1. Install the correct versions of each package, which are listed by the command:

npm info "eslint-config-dina@latest" peerDependencies

If using npm 5+, use this shortcut

npx install-peerdeps --dev eslint-config-dina

If using npm < 5, Linux/OSX users can run

(
  export PKG=eslint-config-dina;
  npm info "$PKG@latest" peerDependencies --json | command sed 's/[\{\},]//g ; s/: /@/g' | xargs npm install --save-dev "$PKG@latest"
)

Which produces and runs a command like:

npm install --save-dev eslint-config-dina eslint@^#.#.# eslint-plugin-jsx-a11y@^#.#.# eslint-plugin-import@^#.#.# eslint-plugin-react@^#.#.#

If using npm < 5, Windows users can either install all the peer dependencies manually, or use the install-peerdeps cli tool.

npm install -g install-peerdeps
install-peerdeps --dev eslint-config-dina

The cli will produce and run a command like:

npm install --save-dev eslint-config-dina eslint@^#.#.# eslint-plugin-jsx-a11y@^#.#.# eslint-plugin-import@^#.#.# eslint-plugin-react@^#.#.#

1. Add "extends": "dina" to your .eslintrc

eslint-config-dina/whitespace

This entry point only errors on whitespace rules and sets all other rules to warnings. View the list of whitespace rules here.

eslint-config-dina/base

This entry point is deprecated. See eslint-config-dina-base.

eslint-config-dina/legacy

This entry point is deprecated. See eslint-config-dina-base.

See Digital Natives' Javascript styleguide and the ESlint config docs for more information.

Improving this config

Consider adding test cases if you're making complicated rules changes, like anything involving regexes. Perhaps in a distant future, we could use literate programming to structure our README as test cases for our .eslintrc?

You can run tests with npm test.

You can make sure this module lints with itself using npm run lint.