Catch bugs and style problems in TypeScript code before running it, so your team ships cleaner code faster.
Enforce consistent coding rules across a team using a shared config file everyone inherits.
Automatically fix certain style issues in your codebase without manually editing files.
Reference deprecated TSLint rules when migrating an old TypeScript project to typescript-eslint.
| palantir/tslint | genkit-ai/genkit | promptslab/awesome-prompt-engineering | |
|---|---|---|---|
| Stars | 5,908 | 5,910 | 5,912 |
| Language | TypeScript | TypeScript | TypeScript |
| Setup difficulty | easy | moderate | easy |
| Complexity | 2/5 | 3/5 | 1/5 |
| Audience | developer | developer | general |
Figures from each repo's GitHub metadata at analysis time.
TSLint is deprecated, use typescript-eslint for new projects. For reference or migration only: install via npm, add a tslint.json config, and run tslint against your source files.
TSLint was a static analysis tool for TypeScript, the typed variant of JavaScript. A linter like TSLint reads your source code without running it and flags problems: style inconsistencies, potential bugs, code that is hard to maintain, and patterns that do not follow the rules your team has agreed on. It was created by Palantir and became widely adopted across the TypeScript community. An important note at the top of the README: TSLint is deprecated. Development stopped, and the community has moved to typescript-eslint, which is a set of TypeScript-specific rules that run inside ESLint. If you are starting a new TypeScript project today, you would use typescript-eslint rather than TSLint. Existing projects using TSLint are encouraged to migrate. When it was active, TSLint supported a large set of built-in rules covering readability and functionality checks, the ability to write custom rules, multiple output formats for reporting violations, and comment flags to disable specific rules on individual lines of code. It could automatically fix certain style violations. It integrated with most editors and build tools of the era, including VS Code, WebStorm, Vim, Emacs, Sublime Text, Eclipse, Atom, Grunt, Gulp, and MSBuild. The configuration system used a JSON file where you could extend shared presets (such as tslint:latest or tslint-react) and add or override rules. A sandbox environment called TSLint Playground was available for testing rules interactively without setting up a project. Third-party rule packages extended TSLint's built-in rules. Community contributions covered areas like Angular, React, RxJS, immutability enforcement, and rules inspired by the Clean Code programming philosophy.
TSLint was a static analysis (linting) tool for TypeScript that caught bugs, style issues, and bad patterns before you run your code. It is now deprecated, new projects should use typescript-eslint instead.
Mainly TypeScript. The stack also includes TypeScript, Node.js, ESLint.
License not mentioned in the explanation.
Setup difficulty is rated easy, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.