Disclaimer: this package is made for our internal usage and is only open source for convenience so we might not consider Pull Requests or Issues. Feel free to fork though.
This package includes the different styles we apply to our JavaScript and TypeScript code.
In order to integrate ESLint
into VS Code
, install these two extensions:
Then add these settings to your VSCode’s settings.json
:
"eslint.format.enable": true,
"editor.defaultFormatter": "dbaeumer.vscode-eslint",
"[javascript]": {
"editor.defaultFormatter": "dbaeumer.vscode-eslint"
},
"[javascriptreact]": {
"editor.defaultFormatter": "dbaeumer.vscode-eslint"
},
"[typescript]": {
"editor.defaultFormatter": "dbaeumer.vscode-eslint"
},
"[typescriptreact]": {
"editor.defaultFormatter": "dbaeumer.vscode-eslint"
},
"[graphql]": {
"editor.defaultFormatter": "dbaeumer.vscode-eslint"
},
"[json]": {
"editor.defaultFormatter": "dbaeumer.vscode-eslint"
}
If the linter does not work right away, you can pop the VS Code
command palette with ⌘ Cmd + ↑ Shift + P
on mac, or Ctrl + ↑ Shift + P
on windows/linux, and set the default formatter:
For more information, check this part of the ESLint documentation.
Vim users could use ALE and use let g:ale_fix_on_save = 1
and eslint
as the linter for JavaScript and TypeScript.
To enforce consistency throughout our imports and exports, we are using eslint-plugin-import.
The set of rules we chose to organize our imports are the following groups:
-
Built in and externals
-
Parents, siblings, indexes and path aliases
import { IncomingMessage, ServerResponse } from "http";
import React from "react"
import { CustomError } from "@src/errors"
import { Handler } from "./handler";
For export rules, we are using: - group-exports. - exports-last.
This plugin offer several configurations depending on your project type.
yarn add -D @fewlines/eslint-config eslint \
eslint-config-prettier eslint-plugin-prettier prettier \
eslint-plugin-import
Then add these lines to your package.json:
"eslintConfig": {
"extends": "@fewlines/eslint-config/node"
}
yarn add -D @fewlines/eslint-config eslint \
eslint-config-prettier eslint-plugin-prettier prettier \
@typescript-eslint/eslint-plugin @typescript-eslint/parser \
eslint-plugin-import
Then add these lines to your package.json:
"eslintConfig": {
"extends": "@fewlines/eslint-config/typescript"
}
The TypeScript plugin extends the previous Node plugin so it is not needed.
yarn add -D @fewlines/eslint-config eslint \
eslint-config-prettier eslint-plugin-prettier prettier \
eslint-plugin-react \
eslint-plugin-import
Then add these lines to your package.json:
"eslintConfig": {
"extends": "@fewlines/eslint-config/react"
}
The React plugin extends the previous Node plugin so it is not needed.
prop-types
checks. You should use it along the react
and typescript
presets.
yarn add -D @fewlines/eslint-config eslint \
eslint-config-prettier eslint-plugin-prettier prettier \
@typescript-eslint/eslint-plugin @typescript-eslint/parser \
eslint-plugin-react \
eslint-plugin-import
Then add these lines to your package.json
:
"eslintConfig": {
"extends": [
"@fewlines/eslint-config/typescript",
"@fewlines/eslint-config/react",
"@fewlines/eslint-config/react-typescript"
]
}
The React + Typescript plugin extends the previous Node plugin so it is not needed.
yarn add -D @fewlines/eslint-config eslint \
eslint-config-prettier eslint-plugin-prettier prettier \
@typescript-eslint/eslint-plugin @typescript-eslint/parser \
eslint-plugin-import
Then add these lines to your package.json
:
"eslintConfig": {
"extends": "@fewlines/eslint-config/preact-typescript"
}
The Preact + Typescript plugin extends the previous Node plugin so it is not needed.
See CONTRIBUTING.md.