eslint-config-ccs

This package provides Childhood Cancer Society's .eslintrc as an extensible shared config.

TODO

• Re-write tests to make them work with typescript
• Move prettier rules to a completely separate package to not add the peerdep by default
• Move ts rules to a completely separate package to not add the typescript peerdeps by default

Usage

We export three ESLint configurations for your usage.

eslint-config-ccs

Our default export contains most of our ESLint rules, including ECMAScript 6+ and React. It requires eslint, eslint-plugin-import, eslint-plugin-react, eslint-plugin-react-hooks, and eslint-plugin-jsx-a11y. Note that it does not enable our React Hooks rules. To enable those, see the eslint-config-ccs/hooks section.

If you don't need React, see eslint-config-airbnb-base.

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

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

If using npm 5+, use this shortcut

npx install-peerdeps --dev eslint-config-ccs

If using yarn, you can also use the shortcut described above if you have npm 5+ installed on your machine, as the command will detect that you are using yarn and will act accordingly. Otherwise, run npm info "eslint-config-ccs@latest" peerDependencies to list the peer dependencies and versions, then run yarn add --dev <dependency>@<version> for each listed peer dependency.

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

(
  export PKG=eslint-config-ccs;
  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-ccs eslint@^#.#.# eslint-plugin-jsx-a11y@^#.#.# eslint-plugin-import@^#.#.# eslint-plugin-react@^#.#.# eslint-plugin-react-hooks@^#.#.#

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

The cli will produce and run a command like:

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

2. Add "extends": "ccs" to your .eslintrc

eslint-config-ccs/hooks

This entry point enables the linting rules for React hooks (requires v16.8+). To use, add "extends": ["ccs", "ccs/hooks"] to your .eslintrc.

eslint-config-ccs/whitespace

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

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.