Skip to content
🚦 An extensible linter for the TypeScript language
Branch: master
Clone or download
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.circleci
.github
.vscode
bin [New rule] add fileNameCasing rule (#3978) Jun 26, 2018
docs Fix typo in rule docs generation (#4638) Apr 4, 2019
scripts
src
test Fix interface name rule handling of numeric characters (#4626) Apr 4, 2019
.editorconfig Switch to tslint-plugin-prettier, clean up rule options config syntax ( Feb 2, 2019
.gitattributes
.gitignore Switch to tslint-plugin-prettier, clean up rule options config syntax ( Feb 2, 2019
.npmignore
.nycrc
CHANGELOG.md
LICENSE
README.md
appveyor.yml Re-ran Prettier on source files again, with some more ignores (#4270) Nov 5, 2018
package.json
tslint-vscode.json
tslint.json
yarn.lock

README.md

NPM version Downloads Dependency Status devDependency Status peerDependency Status Circle CI

TSLint

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:

Installation & Usage

Please refer to the full installation & usage documentation on the TSLint website. There, you'll find information about

Custom Rules & Plugins

Custom rule sets from Palantir

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:

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

Creating a new release

  1. Bump the version number in package.json and src/linter.ts
  2. Add release notes in CHANGELOG.md
    • Use ./scripts/generate-changelog.js (after building it with tsc -p scripts) to generate the changelog diff. This script expects a Github.com personal access token to exist at ~/github_token.txt with "repo" permissions.
  3. Commit with message Prepare release <version>
  4. Push your branch to GitHub and make a PR
  5. Once your PR is merged, wait for the tests to pass on CircleCI for develop
  6. Create a "Release" on GitHub with the proper tag version and notes from the changelog.
    • The tag should be identical to the version in package.json
  7. Run yarn run publish:local
You can’t perform that action at this time.