Alternatives to Prettier logo

Alternatives to Prettier

EditorConfig, ESLint, TSLint, SonarQube, and Stylelint are the most popular alternatives and competitors to Prettier.
4.7K
570
+ 1
7

What is Prettier and what are its top alternatives?

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.
Prettier is a tool in the Code Review category of a tech stack.
Prettier is an open source tool with 44.8K GitHub stars and 3.7K GitHub forks. Here’s a link to Prettier's open source repository on GitHub

Top Alternatives to Prettier

  • EditorConfig
    EditorConfig

    It is a file format and collection of text editor plugins. It helps maintain consistent coding styles for multiple developers working on the same project across various editors and IDEs. ...

  • ESLint
    ESLint

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

  • TSLint
    TSLint

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

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

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

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

  • JSHint
    JSHint

    It is a community-driven tool to detect errors and potential problems in JavaScript code. It is open source and can easily adjust in the environment you expect your code to execute. ...

Prettier alternatives & related posts

EditorConfig logo

EditorConfig

166
57
0
A file format and collection of text editor plugins for maintaining consistent coding styles
166
57
+ 1
0
PROS OF EDITORCONFIG
    Be the first to leave a pro
    CONS OF EDITORCONFIG
      Be the first to leave a con

      related EditorConfig posts

      ESLint logo

      ESLint

      22.2K
      11.8K
      28
      The fully pluggable JavaScript code quality tool
      22.2K
      11.8K
      + 1
      28
      PROS OF ESLINT
      • 8
        Consistent javascript - opinions don't matter anymore
      • 6
        Free
      • 6
        IDE Integration
      • 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 · 5.3M 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 · | 23 upvotes · 1.8M 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
        TSLint logo

        TSLint

        2K
        226
        0
        An extensible linter for the TypeScript language
        2K
        226
        + 1
        0
        PROS OF TSLINT
          Be the first to leave a pro
          CONS OF TSLINT
            Be the first to leave a con

            related TSLint posts

            Simon Reymann
            Senior Fullstack Developer at QUANTUSflow Software GmbH · | 29 upvotes · 5.3M 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 · | 23 upvotes · 1.8M 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
            SonarQube logo

            SonarQube

            1.6K
            1.8K
            49
            Continuous Code Quality
            1.6K
            1.8K
            + 1
            49
            PROS OF SONARQUBE
            • 25
              Tracks code complexity and smell trends
            • 16
              IDE Integration
            • 8
              Complete code Review
            CONS OF SONARQUBE
            • 7
              Sales process is long and unfriendly
            • 7
              Paid support is poor, techs arrogant and unhelpful
            • 1
              Does not integrate with Snyk

            related SonarQube posts

            Simon Reymann
            Senior Fullstack Developer at QUANTUSflow Software GmbH · | 29 upvotes · 5.3M 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 · 3.3M 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

            806
            90
            6
            A mighty, modern CSS linter
            806
            90
            + 1
            6
            PROS OF STYLELINT
            • 5
              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 · 188.2K 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
              RuboCop logo

              RuboCop

              618
              206
              41
              A Ruby static code analyzer, based on the community Ruby style guide
              618
              206
              + 1
              41
              PROS OF RUBOCOP
              • 9
                Open-source
              • 8
                Completely free
              • 7
                Runs Offline
              • 4
                Follows the Ruby Style Guide by default
              • 4
                Can automatically fix some problems
              • 4
                Customizable
              • 2
                Atom package
              • 2
                Integrates with Vim/Emacs/Atom/Sublime/
              • 1
                Integrates With Custom CMS
              CONS OF RUBOCOP
                Be the first to leave a con

                related RuboCop posts

                Francisco Quintero
                Tech Lead at Dev As Pros · | 7 upvotes · 399.7K views

                For many(if not all) small and medium size business time and cost matter a lot.

                That's why languages, frameworks, tools, and services that are easy to use and provide 0 to productive in less time, it's best.

                Maybe Node.js frameworks might provide better features compared to Rails but in terms of MVPs, for us Rails is the leading alternative.

                Amazon EC2 might be cheaper and more customizable than Heroku but in the initial terms of a project, you need to complete configurationos and deploy early.

                Advanced configurations can be done down the road, when the project is running and making money, not before.

                But moving fast isn't the only thing we care about. We also take the job to leave a good codebase from the beginning and because of that we try to follow, as much as we can, style guides in Ruby with RuboCop and in JavaScript with ESLint and StandardJS.

                Finally, comunication and keeping a good history of conversations, decisions, and discussions is important so we use a mix of Slack and Twist

                See more
                Jerome Dalbert
                Principal Backend Software Engineer at StackShare · | 5 upvotes · 534.3K 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
                Code Climate logo

                Code Climate

                569
                475
                279
                Automated Ruby Code Review
                569
                475
                + 1
                279
                PROS OF CODE CLIMATE
                • 71
                  Auto sync with Github
                • 49
                  Simple grade system that motivates to keep code clean
                • 45
                  Better coding
                • 30
                  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
                Principal Backend Software Engineer at StackShare · | 5 upvotes · 534.3K 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
                JSHint logo

                JSHint

                508
                58
                0
                A Static Code Analysis Tool for JavaScript
                508
                58
                + 1
                0
                PROS OF JSHINT
                  Be the first to leave a pro
                  CONS OF JSHINT
                  • 1
                    Non-intuitive configuration

                  related JSHint posts

                  Joshua Dean Küpper
                  CEO at Scrayos UG (haftungsbeschränkt) · | 1 upvote · 37.7K views

                  We use ESLint because we like to remove the general thinking-overhead when writing software. ESLint offers many presets, while also providing users with a lot of customization features. We use ESLint in conjunction with the javascript "standard" configuration (and for our vueJS-projects the "recommended" settings).

                  The other option we considered was JSHint, but we scrapped that, as forward-compatibility is essential for us and ESLint is more fast-paced in its development and supports ESnext natively.

                  See more