Alternatives to TSLint logo

Alternatives to TSLint

ESLint, React Native, Prettier, SonarLint, and SonarQube are the most popular alternatives and competitors to TSLint.
1.5K
213
+ 1
0

What is TSLint and what are its top alternatives?

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 is a tool in the Code Review category of a tech stack.

Top Alternatives to TSLint

  • ESLint
    ESLint

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

  • React Native
    React Native

    React Native enables you to build world-class application experiences on native platforms using a consistent developer experience based on JavaScript and React. The focus of React Native is on developer efficiency across all the platforms you care about - learn once, write anywhere. Facebook uses React Native in multiple production apps and will continue investing in React Native. ...

  • Prettier
    Prettier

    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. ...

  • SonarLint
    SonarLint

    It is an IDE extension that helps you detect and fix quality issues as you write code. Like a spell checker, it squiggles flaws so that they can be fixed before committing code. ...

  • 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. ...

  • Stylelint
    Stylelint

    A mighty, modern CSS linter that helps you enforce consistent conventions and avoid errors in your stylesheets. ...

  • Snyk
    Snyk

    Automatically find & fix vulnerabilities in your code, containers, Kubernetes, and Terraform ...

  • 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. ...

TSLint alternatives & related posts

ESLint logo

ESLint

18.7K
10.2K
25
The fully pluggable JavaScript code quality tool
18.7K
10.2K
+ 1
25
PROS OF ESLINT
  • 7
    Consistent javascript - opinions don't matter anymore
  • 5
    IDE Integration
  • 5
    Free
  • 4
    Customizable
  • 2
    Focuses code review on quality not style
  • 2
    Broad ecosystem of support & users
CONS OF ESLINT
    Be the first to leave a con

    related ESLint posts

    Simon Reymann
    Senior Fullstack Developer at QUANTUSflow Software GmbH · | 29 upvotes · 4.2M views

    Our whole DevOps stack consists of the following tools:

    • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
    • Respectively Git as revision control system
    • SourceTree as Git GUI
    • Visual Studio Code as IDE
    • CircleCI for continuous integration (automatize development process)
    • Prettier / TSLint / ESLint as code linter
    • SonarQube as quality gate
    • Docker as container management (incl. Docker Compose for multi-container application management)
    • VirtualBox for operating system simulation tests
    • Kubernetes as cluster management for docker containers
    • Heroku for deploying in test environments
    • nginx as web server (preferably used as facade server in production environment)
    • SSLMate (using OpenSSL) for certificate management
    • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
    • PostgreSQL as preferred database system
    • Redis as preferred in-memory database/store (great for caching)

    The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

    • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
    • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
    • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
    • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
    • Scalability: All-in-one framework for distributed systems.
    • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
    See more
    Simon Reymann
    Senior Fullstack Developer at QUANTUSflow Software GmbH · | 22 upvotes · 1.2M views

    Our whole Vue.js frontend stack (incl. SSR) consists of the following tools:

    • Nuxt.js consisting of Vue CLI, Vue Router, vuex, Webpack and Sass (Bundler for HTML5, CSS 3), Babel (Transpiler for JavaScript),
    • Vue Styleguidist as our style guide and pool of developed Vue.js components
    • Vuetify as Material Component Framework (for fast app development)
    • TypeScript as programming language
    • Apollo / GraphQL (incl. GraphiQL) for data access layer (https://apollo.vuejs.org/)
    • ESLint, TSLint and Prettier for coding style and code analyzes
    • Jest as testing framework
    • Google Fonts and Font Awesome for typography and icon toolkit
    • NativeScript-Vue for mobile development

    The main reason we have chosen Vue.js over React and AngularJS is related to the following artifacts:

    • Empowered HTML. Vue.js has many similar approaches with Angular. This helps to optimize HTML blocks handling with the use of different components.
    • Detailed documentation. Vue.js has very good documentation which can fasten learning curve for developers.
    • Adaptability. It provides a rapid switching period from other frameworks. It has similarities with Angular and React in terms of design and architecture.
    • Awesome integration. Vue.js can be used for both building single-page applications and more difficult web interfaces of apps. Smaller interactive parts can be easily integrated into the existing infrastructure with no negative effect on the entire system.
    • Large scaling. Vue.js can help to develop pretty large reusable templates.
    • Tiny size. Vue.js weights around 20KB keeping its speed and flexibility. It allows reaching much better performance in comparison to other frameworks.
    See more
    React Native logo

    React Native

    25.9K
    22.5K
    1.1K
    A framework for building native apps with React
    25.9K
    22.5K
    + 1
    1.1K
    PROS OF REACT NATIVE
    • 204
      Learn once write everywhere
    • 166
      Cross platform
    • 162
      Javascript
    • 118
      Native ios components
    • 67
      Built by facebook
    • 62
      Easy to learn
    • 43
      Bridges me into ios development
    • 40
      It's just react
    • 39
      No compile
    • 36
      Declarative
    • 21
      Fast
    • 12
      Virtual Dom
    • 12
      Livereload
    • 11
      Insanely fast develop / test cycle
    • 10
      Great community
    • 9
      Easy setup
    • 9
      Backed by Facebook
    • 9
      It is free and open source
    • 8
      Native android components
    • 7
      Highly customizable
    • 6
      Scalable
    • 6
      Everything component
    • 6
      Awesome
    • 6
      Win win solution of hybrid app
    • 6
      Great errors
    • 5
      Not dependent on anything such as Angular
    • 5
      Simple
    • 4
      OTA update
    • 4
      Awesome, easy starting from scratch
    • 3
      Easy to use
    • 3
      As good as Native without any performance concerns
    • 2
      Web development meets Mobile development
    • 2
      Hot reload
    • 2
      Over the air update (Flutter lacks)
    • 2
      'It's just react'
    • 2
      Many salary
    • 2
      Can be incrementally added to existing native apps
    • 1
      Nigger
    • 1
      Cons
    • 1
      Ngon
    • 0
      Ful
    CONS OF REACT NATIVE
    • 23
      Javascript
    • 18
      Built by facebook
    • 12
      Cant use CSS
    • 4
      30 FPS Limit
    • 2
      Slow
    • 2
      Some compenents not truly native
    • 2
      Generate large apk even for a simple app

    related React Native posts

    Vaibhav Taunk
    Team Lead at Technovert · | 31 upvotes · 1.9M views

    I am starting to become a full-stack developer, by choosing and learning .NET Core for API Development, Angular CLI / React for UI Development, MongoDB for database, as it a NoSQL DB and Flutter / React Native for Mobile App Development. Using Postman, Markdown and Visual Studio Code for development.

    See more

    I'm working as one of the engineering leads in RunaHR. As our platform is a Saas, we thought It'd be good to have an API (We chose Ruby and Rails for this) and a SPA (built with React and Redux ) connected. We started the SPA with Create React App since It's pretty easy to start.

    We use Jest as the testing framework and react-testing-library to test React components. In Rails we make tests using RSpec.

    Our main database is PostgreSQL, but we also use MongoDB to store some type of data. We started to use Redis  for cache and other time sensitive operations.

    We have a couple of extra projects: One is an Employee app built with React Native and the other is an internal back office dashboard built with Next.js for the client and Python in the backend side.

    Since we have different frontend apps we have found useful to have Bit to document visual components and utils in JavaScript.

    See more
    Prettier logo

    Prettier

    3.4K
    506
    7
    Prettier is an opinionated code formatter.
    3.4K
    506
    + 1
    7
    PROS OF PRETTIER
    • 2
      Customizable
    • 1
      Open Source
    • 1
      Atom/VSCode package
    • 1
      Follows the Ruby Style Guide by default
    • 1
      Runs offline
    • 1
      Completely free
    CONS OF PRETTIER
      Be the first to leave a con

      related Prettier posts

      Simon Reymann
      Senior Fullstack Developer at QUANTUSflow Software GmbH · | 29 upvotes · 4.2M views

      Our whole DevOps stack consists of the following tools:

      • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
      • Respectively Git as revision control system
      • SourceTree as Git GUI
      • Visual Studio Code as IDE
      • CircleCI for continuous integration (automatize development process)
      • Prettier / TSLint / ESLint as code linter
      • SonarQube as quality gate
      • Docker as container management (incl. Docker Compose for multi-container application management)
      • VirtualBox for operating system simulation tests
      • Kubernetes as cluster management for docker containers
      • Heroku for deploying in test environments
      • nginx as web server (preferably used as facade server in production environment)
      • SSLMate (using OpenSSL) for certificate management
      • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
      • PostgreSQL as preferred database system
      • Redis as preferred in-memory database/store (great for caching)

      The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

      • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
      • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
      • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
      • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
      • Scalability: All-in-one framework for distributed systems.
      • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
      See more
      Simon Reymann
      Senior Fullstack Developer at QUANTUSflow Software GmbH · | 22 upvotes · 1.2M views

      Our whole Vue.js frontend stack (incl. SSR) consists of the following tools:

      • Nuxt.js consisting of Vue CLI, Vue Router, vuex, Webpack and Sass (Bundler for HTML5, CSS 3), Babel (Transpiler for JavaScript),
      • Vue Styleguidist as our style guide and pool of developed Vue.js components
      • Vuetify as Material Component Framework (for fast app development)
      • TypeScript as programming language
      • Apollo / GraphQL (incl. GraphiQL) for data access layer (https://apollo.vuejs.org/)
      • ESLint, TSLint and Prettier for coding style and code analyzes
      • Jest as testing framework
      • Google Fonts and Font Awesome for typography and icon toolkit
      • NativeScript-Vue for mobile development

      The main reason we have chosen Vue.js over React and AngularJS is related to the following artifacts:

      • Empowered HTML. Vue.js has many similar approaches with Angular. This helps to optimize HTML blocks handling with the use of different components.
      • Detailed documentation. Vue.js has very good documentation which can fasten learning curve for developers.
      • Adaptability. It provides a rapid switching period from other frameworks. It has similarities with Angular and React in terms of design and architecture.
      • Awesome integration. Vue.js can be used for both building single-page applications and more difficult web interfaces of apps. Smaller interactive parts can be easily integrated into the existing infrastructure with no negative effect on the entire system.
      • Large scaling. Vue.js can help to develop pretty large reusable templates.
      • Tiny size. Vue.js weights around 20KB keeping its speed and flexibility. It allows reaching much better performance in comparison to other frameworks.
      See more
      SonarLint logo

      SonarLint

      131
      257
      12
      An IDE extension to detect and fix issues as you write code
      131
      257
      + 1
      12
      PROS OF SONARLINT
      • 11
        IDE Integration
      • 1
        Free
      CONS OF SONARLINT
      • 2
        Not Very User Friendly
      • 2
        Non contextual warnings

      related SonarLint posts

      SonarQube logo

      SonarQube

      1.4K
      1.6K
      42
      Continuous Code Quality
      1.4K
      1.6K
      + 1
      42
      PROS OF SONARQUBE
      • 22
        Tracks code complexity and smell trends
      • 13
        IDE Integration
      • 7
        Complete code Review
      CONS OF SONARQUBE
      • 7
        Sales process is long and unfriendly
      • 7
        Paid support is poor, techs arrogant and unhelpful

      related SonarQube posts

      Simon Reymann
      Senior Fullstack Developer at QUANTUSflow Software GmbH · | 29 upvotes · 4.2M views

      Our whole DevOps stack consists of the following tools:

      • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
      • Respectively Git as revision control system
      • SourceTree as Git GUI
      • Visual Studio Code as IDE
      • CircleCI for continuous integration (automatize development process)
      • Prettier / TSLint / ESLint as code linter
      • SonarQube as quality gate
      • Docker as container management (incl. Docker Compose for multi-container application management)
      • VirtualBox for operating system simulation tests
      • Kubernetes as cluster management for docker containers
      • Heroku for deploying in test environments
      • nginx as web server (preferably used as facade server in production environment)
      • SSLMate (using OpenSSL) for certificate management
      • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
      • PostgreSQL as preferred database system
      • Redis as preferred in-memory database/store (great for caching)

      The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

      • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
      • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
      • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
      • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
      • Scalability: All-in-one framework for distributed systems.
      • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
      See more
      Ganesa Vijayakumar
      Full Stack Coder | Technical Lead · | 19 upvotes · 2.8M views

      I'm planning to create a web application and also a mobile application to provide a very good shopping experience to the end customers. Shortly, my application will be aggregate the product details from difference sources and giving a clear picture to the user that when and where to buy that product with best in Quality and cost.

      I have planned to develop this in many milestones for adding N number of features and I have picked my first part to complete the core part (aggregate the product details from different sources).

      As per my work experience and knowledge, I have chosen the followings stacks to this mission.

      UI: I would like to develop this application using React, React Router and React Native since I'm a little bit familiar on this and also most importantly these will help on developing both web and mobile apps. In addition, I'm gonna use the stacks JavaScript, jQuery, jQuery UI, jQuery Mobile, Bootstrap wherever required.

      Service: I have planned to use Java as the main business layer language as I have 7+ years of experience on this I believe I can do better work using Java than other languages. In addition, I'm thinking to use the stacks Node.js.

      Database and ORM: I'm gonna pick MySQL as DB and Hibernate as ORM since I have a piece of good knowledge and also work experience on this combination.

      Search Engine: I need to deal with a large amount of product data and it's in-detailed info to provide enough details to end user at the same time I need to focus on the performance area too. so I have decided to use Solr as a search engine for product search and suggestions. In addition, I'm thinking to replace Solr by Elasticsearch once explored/reviewed enough about Elasticsearch.

      Host: As of now, my plan to complete the application with decent features first and deploy it in a free hosting environment like Docker and Heroku and then once it is stable then I have planned to use the AWS products Amazon S3, EC2, Amazon RDS and Amazon Route 53. I'm not sure about Microsoft Azure that what is the specialty in it than Heroku and Amazon EC2 Container Service. Anyhow, I will do explore these once again and pick the best suite one for my requirement once I reached this level.

      Build and Repositories: I have decided to choose Apache Maven and Git as these are my favorites and also so popular on respectively build and repositories.

      Additional Utilities :) - I would like to choose Codacy for code review as their Startup plan will be very helpful to this application. I'm already experienced with Google CheckStyle and SonarQube even I'm looking something on Codacy.

      Happy Coding! Suggestions are welcome! :)

      Thanks, Ganesa

      See more
      Stylelint logo

      Stylelint

      741
      77
      5
      A mighty, modern CSS linter
      741
      77
      + 1
      5
      PROS OF STYLELINT
      • 4
        Great way to lint your CSS or SCSS
      • 1
        Only complains about real problems
      CONS OF STYLELINT
        Be the first to leave a con

        related Stylelint posts

        Scenario: I want to integrate Prettier in our code base which is currently using ESLint (for .js and .scss both). The project is using gulp.

        It doesn't feel quite right to me to use ESLint, I wonder if it would be better to use Stylelint or Sass Lint instead.

        I completed integrating ESLint + Prettier, Planning to do the same with [ Stylelint || Sasslint || EsLint] + Prettier.

        And have gulp 'fix' on file save (Watcher).

        Any recommendation is appreciated.

        See more
        Zarema Khalilova
        Frontend Team Lead at Uploadcare · | 3 upvotes · 160.7K views
        Shared insights
        on
        ESLintESLintStylelintStylelint
        at

        To avoid code formatting conflicts and keep a high quality of code we use linters. ESLint for #JavaScript, Stylelint for #CSS, remark-lint for #markdown. Good point that tools allow using shareable config, it useful cause we have many projects.

        See more
        Snyk logo

        Snyk

        629
        275
        12
        Automatically find & fix vulnerabilities in your code, containers, Kubernetes, and Terraform
        629
        275
        + 1
        12
        PROS OF SNYK
        • 7
          Github Integration
        • 3
          Free for open source projects
        • 2
          Finds lots of real vulnerabilities
        CONS OF SNYK
          Be the first to leave a con

          related Snyk posts

          Bryan Dady
          SRE Manager at Subsplash · | 3 upvotes · 290.5K views

          I'm beginning to research the right way to better integrate how we achieve SCA / shift-left / SecureDevOps / secure software supply chain. If you use or have evaluated WhiteSource, Snyk, Sonatype Nexus, SonarQube or similar, I would very much appreciate your perspective on strengths and weaknesses and how you selected your ultimate solution. I want to integrate with GitLab CI.

          See more
          Code Climate logo

          Code Climate

          551
          460
          278
          Automated Ruby Code Review
          551
          460
          + 1
          278
          PROS OF CODE CLIMATE
          • 71
            Auto sync with Github
          • 49
            Simple grade system that motivates to keep code clean
          • 45
            Better coding
          • 29
            Free for open source
          • 21
            Hotspots for quick refactoring candidates
          • 15
            Continued encouragement to a have better / cleaner code
          • 13
            Great UI
          • 11
            Makes you a better coder
          • 10
            Duplication Detection
          • 5
            Safe and Secure
          • 2
            Private
          • 1
            Locally Installable API
          • 1
            Uses rubocop
          • 1
            Extremely accurate in telling you the errors
          • 1
            GitHub only
          • 1
            Python inspection
          • 1
            great open community
          • 1
            GitHub integration, status inline in PRs
          CONS OF CODE CLIMATE
          • 2
            Learning curve, static analysis comparable to eslint
          • 1
            Complains about small stylistic decisions

          related Code Climate posts

          Jerome Dalbert
          Senior Backend Engineer at StackShare · | 5 upvotes · 478.7K views

          The continuous integration process for our Rails backend app starts by opening a GitHub pull request. This triggers a CircleCI build and some Code Climate checks.

          The CircleCI build is a workflow that runs the following jobs:

          • check for security vulnerabilities with Brakeman
          • check code quality with RuboCop
          • run RSpec tests in parallel with the knapsack gem, and output test coverage reports with the simplecov gem
          • upload test coverage to Code Climate

          Code Climate checks the following:

          • code quality metrics like code complexity
          • test coverage minimum thresholds

          The CircleCI jobs and Code Climate checks above have corresponding GitHub status checks.

          Once all the mandatory GitHub checks pass and the code+functionality have been reviewed, developers can merge their pull request into our Git master branch. Code is then ready to deploy!

          #ContinuousIntegration

          See more