eslint-config-zillow-typescript

Zillow's ESLint config for TypeScript, following our code conventions

Usage

Note: Unlike other Zillow eslint config plugins, this module is designed to be used in tandem with another extended config such as eslint-config-zillow.

To install with all necessary peerDependencies, use install-peerdeps:

npx install-peerdeps --dev eslint-config-zillow eslint-config-zillow-typescript

All exported configs should be added to your ESlint configuration file extends. For example, in a JSON .eslintrc:

{
  "extends": ["zillow", "zillow-typescript"]
}

Project Config

All flavors of this config expect your tsconfig.json to be in the current working directory (relative to your eslint config), which is extremely common. If it is elsewhere (say, a monorepo leaf), you will need to override various parserOptions:

// .eslintrc.js
module.exports = {
  extends: ['zillow', 'zillow-typescript'],
  parserOptions: {
    tsconfigRootDir: __dirname,
    project: ['./tsconfig.eslint.json', './packages/*/tsconfig.json'],
  },
};

prettier Editor Plugin Integration

Unfortunately, super-useful editor plugins like prettier-atom and prettier-vscode do not load Prettier settings from ESLint config, which is where we load our Prettier options from. To workaround this, add a .prettierrc.js or prettier.config.js file to your repo root with the following content:

module.exports = require('prettier-config-zillow');

Related

• Zillow's overarching ESLint config
• Zillow's Prettier config
• Zillow's Javascript code conventions

Development

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 (from the repo root) with npm test.

You can make sure this module lints with itself using npm run lint (from the repo root).