Package Exports

eslint-config-standard-with-typescript

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (eslint-config-standard-with-typescript) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

eslint-config-standard-with-typescript

An ESLint shareable config for TypeScript that is based on eslint-config-standard and has TypeScript specific rules from @typescript-eslint/eslint-plugin.

Usage

npm install --save-dev eslint-plugin-standard eslint-plugin-promise eslint-plugin-import eslint-plugin-node @typescript-eslint/parser @typescript-eslint/eslint-plugin eslint-config-standard-with-typescript

Yes, I know it is a large number of packages. This is due to a known design flaw in ESLint.

This long list of dependencies includes:

Peer dependencies of eslint-config-standard
the necessary @typescript-eslint/parser; lets ESLint parse TypeScript.
@typescript-eslint/eslint-plugin; ESLint rules for TypeScript.

Here is an example .eslintrc.json:

{
  "extends": "standard-with-typescript",
  "parser": "@typescript-eslint/parser",
  "parserOptions": {
      "project": "./tsconfig.json"
  },
}

There are some more parserOptions you might care about.

Make sure you read about the --ext command line option. And here is a feature request for specifying extensions in the config.

Example command line usage:

npx eslint --ext .js,.ts .