StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. DevOps
  3. Code Review
  4. Code Review
  5. Prettier vs TSLint

Prettier vs TSLint

OverviewDecisionsComparisonAlternatives

Overview

TSLint
TSLint
Stacks3.4K
Followers234
Votes0
Prettier
Prettier
Stacks13.2K
Followers1.3K
Votes7
GitHub Stars51.1K
Forks4.6K

Prettier vs TSLint: What are the differences?

Introduction

Prettier and TSLint are both popular tools used for code formatting and enforcing coding standards. While they serve similar purposes, there are key differences between the two.

  1. Installation and Configuration: Prettier does not require any additional configuration and can be easily installed using a package manager. TSLint, on the other hand, needs to be configured by setting up rules and configuring a tslint.json file for each project.

  2. Scope of Checks: Prettier focuses mainly on formatting code, such as indentation, line length, and spacing. It does not provide extensive checks for semantic or coding errors. TSLint, however, includes a wide range of rules to enforce coding standards, catch potential bugs, and maintain code quality.

  3. Extensibility: Prettier is less flexible and does not allow much customization. It has a fixed set of rules that cannot be altered. TSLint, on the other hand, is highly customizable and allows developers to define their own rules or extend existing ones based on the project's specific requirements.

  4. Integration with Editors: Prettier integrates seamlessly with a variety of editors and IDEs, providing a convenient way to format code on file save or using keyboard shortcuts. TSLint also integrates with editors but is primarily used during the linting process, providing a feedback loop to developers while they write code.

  5. Maintenance and Support: Prettier is actively maintained and regularly updated with new features and bug fixes. TSLint, on the other hand, is gradually being deprecated in favor of ESLint, a more comprehensive tool that combines both linting and code formatting features.

  6. Community Adoption: Prettier has gained significant popularity and is widely adopted by developers across various languages and frameworks. TSLint, while still widely used, has seen a decrease in popularity since the announcement of its deprecation in favor of ESLint.

In summary, Prettier is a code formatter that focuses on code formatting only and is easy to set up, while TSLint is a linter that provides extensive checks for coding standards and allows for greater customization but is being deprecated in favor of ESLint.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on TSLint, Prettier

Budi
Budi

Programmer

Aug 19, 2020

Review

I think you scan skip MongoDB for now and focussing on creating web component with Reactjs or Vue, I would also recommend to use TypeScript for type hinting support.

For styling, learn CSS first then upgrade to SASS/SCSS or LESS (pick one as mostly same concept) to make CSS more maintainable.

Also to improve your skill on both sectors, install linters if available. For TypeScipt, there are TSLint and for styling, i think there are Stylint. Linter will help you adapt to make a clean code and understand how other peoples usually styled their code.

41.6k views41.6k
Comments
Alex
Alex

Software Engineer

Aug 7, 2020

Review

you don't actually have to choose between these tools as they have vastly different purposes. i think its more a matter of understanding how to use them.

while eslint and stylelint are used to notify you about code quality issues, to guide you to write better code, prettier automatically handles code formatting (without notifying me). nothing else.

prettier and eslint both officially discourage using the eslint-plugin-prettier way, as these tools actually do very different things. autofixing with linters on watch isnt a great idea either. auto-fixing should only be done intentionally. you're not alone though, as a lot of devs set this up wrong.

i encourage you to think about what problem you're trying to solve and configure accordingly.

for my teams i set it up like this:

  • eslint, stylelint, prettier locally installed for cli use and ide support
  • eslint config prettier (code formatting rules are not eslints business, so dont warn me about it)
  • vscode workspace config: format on save
  • separate npm scripts for linting, and formatting
  • precommit hooks (husky)

so you can easily integrate with gulp. its just js after all ;)

159k views159k
Comments

Detailed Comparison

TSLint
TSLint
Prettier
Prettier

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.

Prettier is an opinionated code formatter. It enforces a consistent style by parsing your code and re-printing it with its own rules that take the maximum line length into account, wrapping code when necessary.

Extensive set of core rules; Custom lint rules; Custom formatters (failure reporters); Configuration presets; Composition; Automatic fixing of formatting & style violations
An opinionated code formatter; Supports many languages; Integrates with most editors; Has few options; You press save and code is formatted; No need to discuss style in code review; Saves you time and energy
Statistics
GitHub Stars
-
GitHub Stars
51.1K
GitHub Forks
-
GitHub Forks
4.6K
Stacks
3.4K
Stacks
13.2K
Followers
234
Followers
1.3K
Votes
0
Votes
7
Pros & Cons
No community feedback yet
Pros
  • 2
    Customizable
  • 1
    Open Source
  • 1
    Completely free
  • 1
    Runs offline
  • 1
    Follows the Ruby Style Guide by default
Integrations
Vim
Vim
Visual Studio Code
Visual Studio Code
TypeScript
TypeScript
Atom
Atom
WebStorm
WebStorm
Emacs
Emacs
gulp
gulp
Sublime Text
Sublime Text
Visual Studio
Visual Studio
Grunt
Grunt
GraphQL
GraphQL
JavaScript
JavaScript
TypeScript
TypeScript
Flow
Flow
Vue.js
Vue.js
AngularJS
AngularJS
markdown
markdown
YAML
YAML
Less
Less

What are some alternatives to TSLint, Prettier?

Code Climate

Code Climate

After each Git push, Code Climate analyzes your code for complexity, duplication, and common smells to determine changes in quality and surface technical debt hotspots.

Codacy

Codacy

Codacy automates code reviews and monitors code quality on every commit and pull request on more than 40 programming languages reporting back the impact of every commit or PR, issues concerning code style, best practices and security.

Phabricator

Phabricator

Phabricator is a collection of open source web applications that help software companies build better software.

PullReview

PullReview

PullReview helps Ruby and Rails developers to develop new features cleanly, on-time, and with confidence by automatically reviewing their code.

Gerrit Code Review

Gerrit Code Review

Gerrit is a self-hosted pre-commit code review tool. It serves as a Git hosting server with option to comment incoming changes. It is highly configurable and extensible with default guarding policies, webhooks, project access control and more.

SonarQube

SonarQube

SonarQube provides an overview of the overall health of your source code and even more importantly, it highlights issues found on new code. With a Quality Gate set on your project, you will simply fix the Leak and start mechanically improving.

RuboCop

RuboCop

RuboCop is a Ruby static code analyzer. Out of the box it will enforce many of the guidelines outlined in the community Ruby Style Guide.

CodeFactor.io

CodeFactor.io

CodeFactor.io automatically and continuously tracks code quality with every GitHub or BitBucket commit and pull request, helping software developers save time in code reviews and efficiently tackle technical debt.

ESLint

ESLint

A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. Maintain your code quality with ease.

Amazon CodeGuru

Amazon CodeGuru

It is a machine learning service for automated code reviews and application performance recommendations. It helps you find the most expensive lines of code that hurt application performance and keep you up all night troubleshooting, then gives you specific recommendations to fix or improve your code.

Related Comparisons

GitHub
Bitbucket

Bitbucket vs GitHub vs GitLab

GitHub
Bitbucket

AWS CodeCommit vs Bitbucket vs GitHub

Kubernetes
Rancher

Docker Swarm vs Kubernetes vs Rancher

gulp
Grunt

Grunt vs Webpack vs gulp

Graphite
Kibana

Grafana vs Graphite vs Kibana