To help you get started, we've collected the most common ways that tslint is being used within popular public projects.

microsoft / vscode / build / gulpfile.hygiene.js View on Github

let formatted = result.dest.replace(/\r\n/gm, '\n');

			if (original !== formatted) {
				console.error("File not formatted. Run the 'Format Document' command to fix it:", file.relative);
				errorCount++;
			}
			cb(null, file);

		}, err => {
			cb(err);
		});
	});

	const tslintConfiguration = tslint.Configuration.findConfiguration('tslint.json', '.');
	const tslintOptions = { fix: false, formatter: 'json' };
	const tsLinter = new tslint.Linter(tslintOptions);

	const tsl = es.through(function (file) {
		const contents = file.contents.toString('utf8');
		tsLinter.lint(file.relative, contents, tslintConfiguration.results);
		this.emit('data', file);
	});

	let input;

	if (Array.isArray(some) || typeof some === 'string' || !some) {
		const options = { base: '.', follow: true, allowEmpty: true };
		if (some) {
			input = vfs.src(some, options).pipe(filter(all)); // split this up to not unnecessarily filter all a second time
		} else {
			input = vfs.src(all, options);
		}

View more ways to use tslint

TSLint

⚠️ TSLint is deprecated.

> See this issue for more details: Roadmap: TSLint → ESLint. If you're interested in helping with the TSLint/ESLint migration, please check out our OSS Fellowship program.

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 currently supports:

• an extensive set of core rules
• custom lint rules
• custom formatters (failure reporters)
• inline disabling and enabling of rules with comment flags in source code
• 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, Visual Studio code (alternative: use this extension for TS ❤️.2), WebStorm and more

Installation & Usage

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 Playground

There is a sandbox environment for TSLint at palantir.github.io/tslint-playground, which can be used to test rules and see how TSLint works. Issues can be filed against tslint-playground here.

Custom Rules & Plugins

Custom rule sets from Palantir

• tslint-react - Lint rules related to React & JSX.
• tslint-blueprint - Lint rules to enforce best practices with blueprintjs libraries

Custom rule sets from the community

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
• tslint-sonarts - Bug-finding rules based on advanced code models to spot hard to find errors in TypeScript
• tslint-clean-code - A set of TSLint rules inspired by the Clean Code handbook
• rxjs-tslint-rules - TSLint rules for RxJS

Development

Prerequisites:

• node v7+
• yarn v1.0+

Quick Start

git clone git@github.com:palantir/tslint.git --config core.autocrlf=input --config core.eol=lf
yarn
yarn compile
yarn test