TSLint is an extensible static analysis tool that checks TypeScript code for readability, maintainability, and functionality errors. It is widely supported across modern editors & build systems and can be customized with your own lint rules, configurations, and formatters.
TSLint supports:
- custom lint rules
- custom formatters (failure reporters)
- inline disabling and enabling of rules with comment flags
- configuration presets (
tslint:latest,tslint-react, etc.) and plugin composition - automatic fixing of formatting & style violations
- integration with msbuild, grunt, gulp, atom, eclipse, emacs, sublime, vim, visual studio 2015, visual studio 2017 vscode, webstorm, and more
Please refer to the full installation & usage documentation on the TSLint website. There, you'll find information about
- configuration,
- core rules,
- core formatters, and
- customization of TSLint.
- inline disabling and enabling of rules with comment flags
- tslint-react - Lint rules related to React & JSX.
- tslint-blueprint - Lint rules to enforce best practices with blueprintjs libraries
If we don't have all the rules you're looking for, you can either write your own custom rules or use rules implementations developed by the community. The repos below are a good source of custom rules:
- ESLint rules for TSLint - Improve your TSLint with the missing ESLint Rules
- tslint-microsoft-contrib - A set of TSLint rules used on some Microsoft projects
- codelyzer - A set of tslint rules for static code analysis of Angular TypeScript projects
- vrsource-tslint-rules
- tslint-immutable - TSLint rules to disable mutation in TypeScript
- tslint-consistent-codestyle - TSLint rules to enforce consistent code style in TypeScript
Requirements:
nodev7yarnv0.23+
git clone [email protected]:palantir/tslint.git --config core.autocrlf=input --config core.eol=lf
yarn
yarn compile
yarn test- Bump the version number in
package.jsonandsrc/linter.ts - Add release notes in
CHANGELOG.md yarn verifyto build the latest sources from a clean state- Commit with message
Prepare release <version> - Run
npm publish - Create a git tag for the new release and push it (see existing tags here)