eslint-config-qtrade
v1.0.4
Published
JavaScript Style React/JSX support - ESLint Shareable Config
Downloads
17
Maintainers
Readme
eslint-config-qtrade
This package provides Qtrade's .eslintrc as an extensible shared config.
Usage
We export three ESLint configurations for your usage.
eslint-config-airbnb
Our default export contains all of our ESLint rules, including ECMAScript 6+ and React. It requires eslint
, eslint-config-airbnb
,and eslint-config-prettier
.
- Install the correct versions of each package, which are listed by the command:
npm info "eslint-config-qtrade@latest" peerDependencies
If using npm 5+, use this shortcut
npx install-peerdeps --dev eslint-config-qtrade
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-qtrade@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-qtrade;
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-qtrade 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-qtrade
The cli will produce and run a command like:
npm install --save-dev eslint-config-qtrade eslint@^#.#.# eslint-plugin-jsx-a11y@^#.#.# eslint-plugin-import@^#.#.# eslint-plugin-react@^#.#.# eslint-plugin-react-hooks@^#.#.#
- Add
"extends": "qtrade"
to your.eslintrc
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 eslint
.