Alternatives to Phacility logo

Alternatives to Phacility

GitHub, GitLab, Jira, ESLint, and SonarQube are the most popular alternatives and competitors to Phacility.
0
2
+ 1
0

What is Phacility and what are its top alternatives?

A hosted version of Phabricator, that you pay for.
Phacility is a tool in the Code Review category of a tech stack.

Phacility alternatives & related posts

GitHub logo

GitHub

42.6K
33.9K
10K
42.6K
33.9K
+ 1
10K
Powerful collaboration, review, and code management for open source and private development projects
GitHub logo
GitHub
VS
Phacility logo
Phacility

related GitHub posts

Tim Abbott
Tim Abbott
Founder at Zulip · | 16 upvotes · 135.7K views
atZulipZulip
GitLab
GitLab
GitHub
GitHub

I have mixed feelings on GitHub as a product and our use of it for the Zulip open source project. On the one hand, I do feel that being on GitHub helps people discover Zulip, because we have enough stars (etc.) that we rank highly among projects on the platform. and there is a definite benefit for lowering barriers to contribution (which is important to us) that GitHub has such a dominant position in terms of what everyone has accounts with.

But even ignoring how one might feel about their new corporate owner (MicroSoft), in a lot of ways GitHub is a bad product for open source projects. Years after the "Dear GitHub" letter, there are still basic gaps in its issue tracker:

  • You can't give someone permission to label/categorize issues without full write access to a project (including ability to merge things to master, post releases, etc.).
  • You can't let anyone with a GitHub account self-assign issues to themselves.
  • Many more similar issues.

It's embarrassing, because I've talked to GitHub product managers at various open source events about these things for 3 years, and they always agree the thing is important, but then nothing ever improves in the Issues product. Maybe the new management at MicroSoft will fix their product management situation, but if not, I imagine we'll eventually do the migration to GitLab.

We have a custom bot project, http://github.com/zulip/zulipbot, to deal with some of these issues where possible, and every other large project we talk to does the same thing, more or less.

See more
Ali Soueidan
Ali Soueidan
Creative Web Developer at Ali Soueidan · | 16 upvotes · 85.9K views
npm
npm
Babel
Babel
PHP
PHP
Adobe Illustrator
Adobe Illustrator
Asana
Asana
ES6
ES6
GitHub
GitHub
Git
Git
JSON
JSON
Sass
Sass
Pug
Pug
JavaScript
JavaScript
vuex
vuex
Vue.js
Vue.js

Application and Data: Since my personal website ( https://alisoueidan.com ) is a SPA I've chosen to use Vue.js, as a framework to create it. After a short skeptical phase I immediately felt in love with the single file component concept! I also used vuex for state management, which makes working with several components, which are communicating with each other even more fun and convenient to use. Of course, using Vue requires using JavaScript as well, since it is the basis of it.

For markup and style, I used Pug and Sass, since they’re the perfect match to me. I love the clean and strict syntax of both of them and even more that their structure is almost similar. Also, both of them come with an expanded functionality such as mixins, loops and so on related to their “siblings” (HTML and CSS). Both of them require nesting and prevent untidy code, which can be a huge advantage when working in teams. I used JSON to store data (since the data quantity on my website is moderate) – JSON works also good in combo with Pug, using for loops, based on the JSON Objects for example.

To send my contact form I used PHP, since sending emails using PHP is still relatively convenient, simple and easy done.

DevOps: Of course, I used Git to do my version management (which I even do in smaller projects like my website just have an additional backup of my code). On top of that I used GitHub since it now supports private repository for free accounts (which I am using for my own). I use Babel to use ES6 functionality such as arrow functions and so on, and still don’t losing cross browser compatibility.

Side note: I used npm for package management. 🎉

*Business Tools: * I use Asana to organize my project. This is a big advantage to me, even if I work alone, since “private” projects can get interrupted for some time. By using Asana I still know (even after month of not touching a project) what I’ve done, on which task I was at last working on and what still is to do. Working in Teams (for enterprise I’d take on Jira instead) of course Asana is a Tool which I really love to use as well. All the graphics on my website are SVG which I have created with Adobe Illustrator and adjusted within the SVG code or by using JavaScript or CSS (SASS).

See more

related GitLab posts

Tim Abbott
Tim Abbott
Founder at Zulip · | 16 upvotes · 135.7K views
atZulipZulip
GitLab
GitLab
GitHub
GitHub

I have mixed feelings on GitHub as a product and our use of it for the Zulip open source project. On the one hand, I do feel that being on GitHub helps people discover Zulip, because we have enough stars (etc.) that we rank highly among projects on the platform. and there is a definite benefit for lowering barriers to contribution (which is important to us) that GitHub has such a dominant position in terms of what everyone has accounts with.

But even ignoring how one might feel about their new corporate owner (MicroSoft), in a lot of ways GitHub is a bad product for open source projects. Years after the "Dear GitHub" letter, there are still basic gaps in its issue tracker:

  • You can't give someone permission to label/categorize issues without full write access to a project (including ability to merge things to master, post releases, etc.).
  • You can't let anyone with a GitHub account self-assign issues to themselves.
  • Many more similar issues.

It's embarrassing, because I've talked to GitHub product managers at various open source events about these things for 3 years, and they always agree the thing is important, but then nothing ever improves in the Issues product. Maybe the new management at MicroSoft will fix their product management situation, but if not, I imagine we'll eventually do the migration to GitLab.

We have a custom bot project, http://github.com/zulip/zulipbot, to deal with some of these issues where possible, and every other large project we talk to does the same thing, more or less.

See more
Michael Kelly
Michael Kelly
Senior Software Engineer at StackShare · | 14 upvotes · 169.3K views
atACK FoundryACK Foundry
Bitbucket
Bitbucket
GitLab Pages
GitLab Pages
GitLab CI
GitLab CI
GitHub
GitHub
GitLab
GitLab
#OpenSourceCloud

I use GitLab when building side-projects and MVPs. The interface and interactions are close enough to those of GitHub to prevent cognitive switching costs between professional and personal projects hosted on different services.

GitLab also provides a suite of tools including issue/project management, CI/CD with GitLab CI, and validation/landing pages with GitLab Pages. With everything in one place, on an #OpenSourceCloud GitLab makes it easy for me to manage much larger projects on my own, than would be possible with other solutions or tools.

It's petty I know, but I can also read the GitLab code diffs far more easily than diffs on GitHub or Bitbucket...they just look better in my opinion.

See more
Jira logo

Jira

12.1K
8.3K
1.1K
12.1K
8.3K
+ 1
1.1K
The #1 software development tool used by agile teams to plan, track, and release great software.
Jira logo
Jira
VS
Phacility logo
Phacility

related Jira posts

David Ritsema
David Ritsema
Frontend Architect at Herman Miller · | 10 upvotes · 37.7K views
atHerman MillerHerman Miller
GitHub
GitHub
Confluence
Confluence
Jira
Jira

We knew how we wanted to build our Design System, now it was time to choose the tools to get us there. The essence of Scrum is a small team of people. The team is highly flexible and adaptive. Perfect, so we'll work in 2 week sprints where each sprint can be a mix of new R&D stories, a presentation of decisions made, and showcasing key development milestones.

We are also able to run content stories in parallel, focusing development efforts around key areas of the site that our authors need first. Our stories would exist in a Jira backlog, documentation would be hosted in Confluence , and GitHub would host our codebase. If developers identify technical improvements during the sprint, they can be added as GitHub issues and transferred to Jira if we decide to represent them as stories for the Backlog. For Sprint Retrospectives, @groupmap proved to be a great way to include our remote members of the dev team.

This worked well for our team and allowed us to be flexible in what we wanted to build and how we wanted to build it. As we further defined our Backlog and estimated each story, we could accurately measure the team's capacity (velocity) and confidently estimate a launch date.

See more
Priit Kaasik
Priit Kaasik
Engineering Lead at Katana MRP · | 9 upvotes · 56.1K views
atKatana MRPKatana MRP
Papertrail
Papertrail
appear.in
appear.in
Bitbucket
Bitbucket
Confluence
Confluence
Intercom
Intercom
Jira
Jira
Slack
Slack
#RemoteTeam
#Agile
#CustomerSupportChat
#Notes
#SourceCode
#Logging
#Release
#InProductCommunication
#ContinuousDelivery
#Alerts
#Documentation
#Requirements

As a new company we could early adopt and bet on #RemoteTeam setup without cultural baggage derailing us. Our building blocks for developing remote working culture are:

  • Hiring people who are self sufficient, self-disciplined and excel at video and written communication to work remotely
  • Set up periodic ceremonies ( #DailyStandup, #Grooming, Release calls and chats etc) to keep the company rhythm / heartbeat going across remote cells
  • Regularly train your leaders to take into account remote working aspects of organizing f2f calls, events, meetups, parties etc. when communicating and organizing workflows
  • And last, but not least - select the right tools to support effective communication and collaboration:
  1. All feeds and conversations come together in Slack
  2. #Agile workflows in Jira
  3. InProductCommunication and #CustomerSupportChat in Intercom
  4. #Notes, #Documentation and #Requirements in Confluence
  5. #SourceCode and ContinuousDelivery in Bitbucket
  6. Persistent video streams between locations, demos, meetings run on appear.in
  7. #Logging and Alerts in Papertrail
See more

related ESLint posts

Johnny Bell
Johnny Bell
Senior Software Engineer at StackShare · | 17 upvotes · 100.5K views
ESLint
ESLint
Prettier
Prettier
Babel
Babel
npm
npm
Yarn
Yarn
Node.js
Node.js
Webpack
Webpack
#ES5
#ES6

So when starting a new project you generally have your go to tools to get your site up and running locally, and some scripts to build out a production version of your site. Create React App is great for that, however for my projects I feel as though there is to much bloat in Create React App and if I use it, then I'm tied to React, which I love but if I want to switch it up to Vue or something I want that flexibility.

So to start everything up and running I clone my personal Webpack boilerplate - This is still in Webpack 3, and does need some updating but gets the job done for now. So given the name of the repo you may have guessed that yes I am using Webpack as my bundler I use Webpack because it is so powerful, and even though it has a steep learning curve once you get it, its amazing.

The next thing I do is make sure my machine has Node.js configured and the right version installed then run Yarn. I decided to use Yarn because when I was building out this project npm had some shortcomings such as no .lock file. I could probably move from Yarn to npm but I don't really see any point really.

I use Babel to transpile all of my #ES6 to #ES5 so the browser can read it, I love Babel and to be honest haven't looked up any other transpilers because Babel is amazing.

Finally when developing I have Prettier setup to make sure all my code is clean and uniform across all my JS files, and ESLint to make sure I catch any errors or code that could be optimized.

I'm really happy with this stack for my local env setup, and I'll probably stick with it for a while.

See more
Francisco Quintero
Francisco Quintero
Tech Lead at Dev As Pros · | 7 upvotes · 49K views
atDev As ProsDev As Pros
Twist
Twist
Slack
Slack
ESLint
ESLint
JavaScript
JavaScript
RuboCop
RuboCop
Heroku
Heroku
Amazon EC2
Amazon EC2
Rails
Rails
Node.js
Node.js

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
SonarQube logo

SonarQube

527
256
14
527
256
+ 1
14
Continuous Code Quality
SonarQube logo
SonarQube
VS
Phacility logo
Phacility

related SonarQube posts

Ganesa Vijayakumar
Ganesa Vijayakumar
Full Stack Coder | Module Lead · | 15 upvotes · 387.2K views
SonarQube
SonarQube
Codacy
Codacy
Docker
Docker
Git
Git
Apache Maven
Apache Maven
Amazon EC2 Container Service
Amazon EC2 Container Service
Microsoft Azure
Microsoft Azure
Amazon Route 53
Amazon Route 53
Elasticsearch
Elasticsearch
Solr
Solr
Amazon RDS
Amazon RDS
Amazon S3
Amazon S3
Heroku
Heroku
Hibernate
Hibernate
MySQL
MySQL
Node.js
Node.js
Java
Java
Bootstrap
Bootstrap
jQuery Mobile
jQuery Mobile
jQuery UI
jQuery UI
jQuery
jQuery
JavaScript
JavaScript
React Native
React Native
React Router
React Router
React
React

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
Codacy
Codacy
codebeat
codebeat
SonarQube
SonarQube

It is very important to have clean code. To be sure that the code quality is not really bad I use a few tools. I love SonarQube with many relevant hints and deep analysis of code. codebeat isn't so detailed, but it can find complexity issues and duplications. Codacy cannot find more bugs then your IDE. The winner for me is SonarQube that shows me really relevant bugs in my code.

See more

related Code Climate posts

Jerome Dalbert
Jerome Dalbert
Senior Backend Engineer at StackShare · | 5 upvotes · 45.8K views
atStackShareStackShare
Git
Git
Rails
Rails
RSpec
RSpec
RuboCop
RuboCop
Brakeman
Brakeman
Code Climate
Code Climate
CircleCI
CircleCI
GitHub
GitHub
#ContinuousIntegration

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
Prettier logo

Prettier

303
127
0
303
127
+ 1
0
Prettier is an opinionated code formatter.
    Be the first to leave a pro
    Prettier logo
    Prettier
    VS
    Phacility logo
    Phacility

    related Prettier posts

    Johnny Bell
    Johnny Bell
    Senior Software Engineer at StackShare · | 17 upvotes · 100.5K views
    ESLint
    ESLint
    Prettier
    Prettier
    Babel
    Babel
    npm
    npm
    Yarn
    Yarn
    Node.js
    Node.js
    Webpack
    Webpack
    #ES5
    #ES6

    So when starting a new project you generally have your go to tools to get your site up and running locally, and some scripts to build out a production version of your site. Create React App is great for that, however for my projects I feel as though there is to much bloat in Create React App and if I use it, then I'm tied to React, which I love but if I want to switch it up to Vue or something I want that flexibility.

    So to start everything up and running I clone my personal Webpack boilerplate - This is still in Webpack 3, and does need some updating but gets the job done for now. So given the name of the repo you may have guessed that yes I am using Webpack as my bundler I use Webpack because it is so powerful, and even though it has a steep learning curve once you get it, its amazing.

    The next thing I do is make sure my machine has Node.js configured and the right version installed then run Yarn. I decided to use Yarn because when I was building out this project npm had some shortcomings such as no .lock file. I could probably move from Yarn to npm but I don't really see any point really.

    I use Babel to transpile all of my #ES6 to #ES5 so the browser can read it, I love Babel and to be honest haven't looked up any other transpilers because Babel is amazing.

    Finally when developing I have Prettier setup to make sure all my code is clean and uniform across all my JS files, and ESLint to make sure I catch any errors or code that could be optimized.

    I'm really happy with this stack for my local env setup, and I'll probably stick with it for a while.

    See more
    Russel Werner
    Russel Werner
    Lead Engineer at StackShare · | 7 upvotes · 36.9K views
    atStackShareStackShare
    Visual Studio Code
    Visual Studio Code
    WebStorm
    WebStorm
    ESLint
    ESLint
    Prettier
    Prettier

    We use Prettier because when we rebooted our front-end stack, I decided that it would be an efficient use of our time to not worry about code formatting issues and personal preferences during peer review. Prettier eliminates this concern by auto-formatting our code to a deterministic output. We use it along with ESLint and have 1st-class support in our WebStorm and Visual Studio Code editors.

    See more

    related Codacy posts

    Ganesa Vijayakumar
    Ganesa Vijayakumar
    Full Stack Coder | Module Lead · | 15 upvotes · 387.2K views
    SonarQube
    SonarQube
    Codacy
    Codacy
    Docker
    Docker
    Git
    Git
    Apache Maven
    Apache Maven
    Amazon EC2 Container Service
    Amazon EC2 Container Service
    Microsoft Azure
    Microsoft Azure
    Amazon Route 53
    Amazon Route 53
    Elasticsearch
    Elasticsearch
    Solr
    Solr
    Amazon RDS
    Amazon RDS
    Amazon S3
    Amazon S3
    Heroku
    Heroku
    Hibernate
    Hibernate
    MySQL
    MySQL
    Node.js
    Node.js
    Java
    Java
    Bootstrap
    Bootstrap
    jQuery Mobile
    jQuery Mobile
    jQuery UI
    jQuery UI
    jQuery
    jQuery
    JavaScript
    JavaScript
    React Native
    React Native
    React Router
    React Router
    React
    React

    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
    Codacy
    Codacy
    codebeat
    codebeat
    SonarQube
    SonarQube

    It is very important to have clean code. To be sure that the code quality is not really bad I use a few tools. I love SonarQube with many relevant hints and deep analysis of code. codebeat isn't so detailed, but it can find complexity issues and duplications. Codacy cannot find more bugs then your IDE. The winner for me is SonarQube that shows me really relevant bugs in my code.

    See more

    related RuboCop posts

    Francisco Quintero
    Francisco Quintero
    Tech Lead at Dev As Pros · | 7 upvotes · 49K views
    atDev As ProsDev As Pros
    Twist
    Twist
    Slack
    Slack
    ESLint
    ESLint
    JavaScript
    JavaScript
    RuboCop
    RuboCop
    Heroku
    Heroku
    Amazon EC2
    Amazon EC2
    Rails
    Rails
    Node.js
    Node.js

    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
    Jerome Dalbert
    Senior Backend Engineer at StackShare · | 5 upvotes · 45.8K views
    atStackShareStackShare
    Git
    Git
    Rails
    Rails
    RSpec
    RSpec
    RuboCop
    RuboCop
    Brakeman
    Brakeman
    Code Climate
    Code Climate
    CircleCI
    CircleCI
    GitHub
    GitHub
    #ContinuousIntegration

    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
    TSLint logo

    TSLint

    112
    38
    0
    112
    38
    + 1
    0
    An extensible linter for the TypeScript language
      Be the first to leave a pro
      TSLint logo
      TSLint
      VS
      Phacility logo
      Phacility

      related TSLint posts

      Forrest Norvell
      Forrest Norvell
      engineering manager at self-employed · | 6 upvotes · 17K views
      Visual Studio Code
      Visual Studio Code
      Flow (JS)
      Flow (JS)
      ESLint
      ESLint
      TSLint
      TSLint
      TypeScript
      TypeScript

      I use TypeScript because the tooling is more mature (the decision to discontinue TSLint in favor of moving all its checks to ESLint is a thoughtful and mature decision), there's a ton of examples and tutorials for it, and it just generally seems to be where the industry is headed. Flow (JS) is a fine tool, but it just hasn't seen the uptake that TS has, and as a result is lacking a lot of the nicer small things, like thorough Visual Studio Code integration, offered by TS.

      See more
      Stylelint logo

      Stylelint

      81
      26
      1
      81
      26
      + 1
      1
      A mighty, modern CSS linter
      Stylelint logo
      Stylelint
      VS
      Phacility logo
      Phacility

      related Stylelint posts

      Zarema Khalilova
      Zarema Khalilova
      Frontend Team Lead at Uploadcare · | 3 upvotes · 15K views
      atUploadcareUploadcare
      Stylelint
      Stylelint
      ESLint
      ESLint
      #Markdown
      #JavaScript

      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

      77
      50
      0
      77
      50
      + 1
      0
      Fix vulnerabilities in Node & npm dependencies with a click
        Be the first to leave a pro
        Snyk logo
        Snyk
        VS
        Phacility logo
        Phacility
        Crucible logo

        Crucible

        32
        25
        10
        32
        25
        + 1
        10
        Review code, discuss changes, share knowledge, and identify defects
        Crucible logo
        Crucible
        VS
        Phacility logo
        Phacility
        EditorConfig logo

        EditorConfig

        30
        8
        0
        30
        8
        + 1
        0
        A file format and collection of text editor plugins for maintaining consistent coding styles
          Be the first to leave a pro
          EditorConfig logo
          EditorConfig
          VS
          Phacility logo
          Phacility
          Standard JS logo

          Standard JS

          30
          7
          0
          30
          7
          + 1
          0
          A JavaScript Standard Style
            Be the first to leave a pro
            Standard JS logo
            Standard JS
            VS
            Phacility logo
            Phacility
            Hound logo

            Hound

            29
            29
            13
            29
            29
            + 1
            13
            A hosted service that comments on Ruby style guide violations in your GitHub pull requests
            Hound logo
            Hound
            VS
            Phacility logo
            Phacility