Alternatives to scss-lint logo

Alternatives to scss-lint

Sass Lint , Stylelint, ESLint, Prettier, and SonarQube are the most popular alternatives and competitors to scss-lint.
99
60
+ 1
0

What is scss-lint and what are its top alternatives?

It is a tool to help keep your SCSS files clean and readable by running it against a collection of configurable linter rules. You can run it manually from the command line, or integrate it into your SCM hooks.
scss-lint is a tool in the Code Review category of a tech stack.
scss-lint is an open source tool with 3.5K GitHub stars and 490 GitHub forks. Here’s a link to scss-lint's open source repository on GitHub

Top Alternatives to scss-lint

  • Sass Lint

    Sass Lint

    It is a Node-only Sass linter for both sass and scss syntax. It can be run through a command line interface. Special comments can be used to disable and enable certain rules throughout your source files in a variety of scenarios. ...

  • Stylelint

    Stylelint

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

  • ESLint

    ESLint

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

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

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

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

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

scss-lint alternatives & related posts

Sass Lint  logo

Sass Lint

26
32
0
Pure Node.js Sass linting
26
32
+ 1
0
PROS OF SASS LINT
    Be the first to leave a pro
    CONS OF SASS LINT
      Be the first to leave a con

      related Sass Lint 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
      Stylelint logo

      Stylelint

      586
      69
      5
      A mighty, modern CSS linter
      586
      69
      + 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 · 144.4K 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
        ESLint logo

        ESLint

        15.2K
        8.5K
        23
        The fully pluggable JavaScript code quality tool
        15.2K
        8.5K
        + 1
        23
        PROS OF ESLINT
        • 7
          Consistent javascript - opinions don't matter anymore
        • 5
          IDE Integration
        • 4
          Free
        • 3
          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 · | 28 upvotes · 3.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 · | 20 upvotes · 789.1K 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
          Prettier logo

          Prettier

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

            related Prettier posts

            Simon Reymann
            Senior Fullstack Developer at QUANTUSflow Software GmbH · | 28 upvotes · 3.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 · | 20 upvotes · 789.1K 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.3K
            1.4K
            39
            Continuous Code Quality
            1.3K
            1.4K
            + 1
            39
            PROS OF SONARQUBE
            • 20
              Tracks code complexity and smell trends
            • 12
              IDE Integration
            • 7
              Complete code Review
            CONS OF SONARQUBE
            • 5
              Sales process is long and unfriendly
            • 4
              Paid support is poor, techs arrogant and unhelpful

            related SonarQube posts

            Simon Reymann
            Senior Fullstack Developer at QUANTUSflow Software GmbH · | 28 upvotes · 3.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 | Module Lead · | 19 upvotes · 2.5M 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
            TSLint logo

            TSLint

            902
            188
            0
            An extensible linter for the TypeScript language
            902
            188
            + 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 · | 28 upvotes · 3.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 · | 20 upvotes · 789.1K 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
                Snyk logo

                Snyk

                569
                209
                8
                Automatically find & fix vulnerabilities in your code, containers, Kubernetes, and Terraform
                569
                209
                + 1
                8
                PROS OF SNYK
                • 5
                  Github Integration
                • 2
                  Free for open source projects
                • 1
                  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 · 244.3K 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

                  536
                  442
                  276
                  Automated Ruby Code Review
                  536
                  442
                  + 1
                  276
                  PROS OF CODE CLIMATE
                  • 70
                    Auto sync with Github
                  • 49
                    Simple grade system that motivates to keep code clean
                  • 44
                    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
                  • 1
                    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 · 440.8K 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