Current Support

Currently this package provides Typescript configurations for:

• Typescript vanilla JS
• Typescript React
• Typescript Svelte
• Typescript Node
• Typescript Jest

Non-Typescript Rule Definitions

This package extends all of the rules defined in our core eslint-config package, @ascend-innovations/eslint-config. The only difference is that it adds overrides that define rules & handling for typescript files.

Installing

1. Put a .eslintrc (or any valid eslint config file) in your project root
2. You can alternatively put the config in your package.json under the property "eslintConfig":. This makes one less file in your project.
3. Be sure your to have a valid tsconfig.json configured for your project.
4. Install dependencies and select the configuration you want (available configs listed below)

Default Vanilla JS Configuration

The default install will install all required AND optional dependencies. You can safely remove the following packages without triggering a peer dependency warning if you aren't consuming the associated configs:

• react
  • eslint-config-airbnb, eslint-plugin-react, eslint-plugin-react-hooks, eslint-plugin-jsx-a11y
• jest
  • eslint-plugin-jest
• svelte
  • eslint-plugin-svelte3

Install it with NPM: npx install-peerdeps --dev @ascend-innovations/eslint-config-ts
Install it with Yarn: npx install-peerdeps --dev @ascend-innovations/eslint-config-ts -Y
Use it:

{
  "extends": [
    "@ascend-innovations/eslint-config-ts"
  ]
}

Notes:

• This install will install optional peer dependencies as well. If you aren't using react or jest, you can remove the following packages without triggering a peer dependency warning:
  • eslint-config-airbnb, eslint-plugin-react, eslint-plugin-react-hooks, eslint-plugin-jsx-a11y
• Extends eslint-config-airbnb-base
• Prettier is always on (configured & enabled by default)

React Configuration

Use it:

{
  "extends": [
    "@ascend-innovations/eslint-config-ts/react"
  ]
}

Notes:

• Extends eslint-config-airbnb

Svelte Configuration

Use it: Svelte is a bit finicky with linting setups, so we keep Svelte stuff in it's own config to apply on top of the root config. This gives us greater control and makes debugging easier.

{
  "extends": [
    "@ascend-innovations/eslint-config-ts",
    "@ascend-innovations/eslint-config-ts/svelte"
  ]
}

Node Configuration

Use it:

{
  "extends": [
    "@ascend-innovations/eslint-config-ts/node"
  ]
}

Notes:

• Extends eslint-config-airbnb-base

Add Jest Support

You can add Jest support to any project:

{
  "extends": [
    "@ascend-innovations/eslint-config-ts/jest"
  ]
}

Set Up Project Lint Scripts

Add two scripts to your package.json to lint and/or fix:

Non-React projects:

"scripts": {
  "lint": "eslint . --ext .js,.ts",
  "lint:fix": "eslint . --ext .js,.ts --fix"
},

React projects:

"scripts": {
  "lint": "eslint . --ext .js,.ts,.jsx,.tsx",
  "lint:fix": "eslint . --ext .js,.ts,.jsx,.tsx --fix"
},

Now you can manually lint your code by running npm run lint and fix all fixable issues with npm run lint:fix.

With VS Code

We highly recommend configuring your editor to do this automatically on file save across your whole project.

1. Install the ESLint plugin for VSCode
2. Create a file in your current project in .vscode/settings.json.
3. Place the following configuration in the file:

{
    // show eslint icon at bottom toolbar
    "eslint.alwaysShowStatus": true,

    //
    // Auto-run code formatting on save
    //
    "editor.formatOnSave": true,

    // Tell the ESLint plugin to run on save
    "editor.codeActionsOnSave": {
        "source.fixAll.eslint": true
    },

    // The following prevents linting from running twice
    // turn it off for JS and JSX, we will do this via eslint
    "[javascript]": {
      "editor.formatOnSave": false
    },
    "[javascriptreact]": {
        "editor.formatOnSave": false
    },
    // Turn it off for TS & TSX
    "[typescript]": {
        "editor.formatOnSave": false
    },
    "[typescriptreact]": {
        "editor.formatOnSave": false
    },
    "[svelte]": {
        "editor.formatOnSave": false
    },

}

4. In order to ensure there are no conflicts between Prettier and ESLint with any plugins you may have active in your VSCode editor, we also recommend adding a file at .vscode/extensions.json with the following content:

{
    // See http://go.microsoft.com/fwlink/?LinkId=827846 to learn about workspace recommendations.
    // List of extensions which should be recommended for users of this workspace.
    "recommendations": [
        "dbaeumer.vscode-eslint"
    ],
    // List of extensions recommended by VS Code that should not be recommended for users of this workspace.
    "unwantedRecommendations": [
        "esbenp.prettier-vscode", // You don't need the prettier extension with this setup
        "editorconfig.editorconfig", // You don't need editor config with this setup
    ]
}

This will make sure that anyone working on the project is aware of enabling/disabling proper extensions!