Skip to content
This repository has been archived by the owner on Mar 25, 2021. It is now read-only.

palantir/tslint

Folders and files

NameName
Last commit message
Last commit date

Latest commit

1899ed8 Â· Jan 10, 2019
Dec 11, 2018
Jul 25, 2018
Nov 13, 2018
Jun 26, 2018
Dec 12, 2018
Dec 12, 2018
Jan 10, 2019
Jan 10, 2019
Jul 23, 2017
Oct 31, 2017
Jul 23, 2018
Nov 15, 2017
Apr 5, 2017
Nov 5, 2018
Nov 5, 2018
Dec 18, 2018
Nov 10, 2016
Dec 12, 2018
Nov 5, 2018
Jan 10, 2019
Dec 12, 2018
Dec 15, 2018

Repository files navigation

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 [email protected]: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