Need advice about which tool to choose?Ask the StackShare community!
ESLint vs PHPStan: What are the differences?
Introduction
Here, we will discuss the key differences between ESLint and PHPStan. Both tools are widely used for code analysis in different programming languages and offer unique features that cater to the specific needs of their respective ecosystems.
Architecture: ESLint is primarily designed for JavaScript and follows a modular architecture that allows users to enable/disable specific rules based on their project requirements. On the other hand, PHPStan is built specifically for PHP and provides static analysis of the codebase without the need for explicit configuration.
Language Support: ESLint focuses solely on JavaScript and its various frameworks and libraries, providing a wide range of customizable rules and plugins. PHPStan, on the other hand, is dedicated to PHP and has in-depth knowledge of the PHP language and its specific coding standards.
Type Checking: ESLint offers limited support for type checking by using third-party plugins like TypeScript ESLint, Flow, etc. However, its primary focus is on linting and enforcing code style. PHPStan, in contrast, excels in type checking and performs advanced static analysis to detect type-related issues, such as invalid function arguments or incompatible type assignments.
Integration: Both ESLint and PHPStan can be easily integrated into modern development workflows. However, ESLint has better integration with popular code editors and build tools for JavaScript, making it more convenient for developers working on JavaScript projects. PHPStan integrates well with popular PHP frameworks and can be used as part of continuous integration pipelines.
Community Support: ESLint has a larger and more active community due to its wider adoption in the JavaScript ecosystem. This leads to extensive plugin and configuration options, making it highly customizable. PHPStan, although having a growing community, still lacks some of the features and customizability that ESLint offers.
In Summary, the key differences between ESLint and PHPStan lie in their language support, architecture, type checking capabilities, integration options, and community support. While ESLint is highly flexible and widely used for JavaScript linting, PHPStan provides comprehensive analysis specifically for PHP code, especially in terms of type checking.
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.
In the case of .js files I would recommend using both Eslint and Prettier.
You can set up Prettier as an Eslint rule using the following plugin:
https://github.com/prettier/eslint-plugin-prettier
And in order to avoid conflicts between Prettier and Eslint, you can use this config:
https://github.com/prettier/eslint-config-prettier
Which turns off all Eslint rules that are unnecessary or might conflict with Prettier.
Pura vida! Well, I had a similar issue and at the end I decided to use Stylelint + Prettier for that job, in our case, we wanted that our linting process includes the SCSS files and not only the JS file, base on that we concluded that using only ESLint to do both things wasn't the best option, so, we integrated prettier with Stylelint, and for that we used a neat plugin that allowed us to use Prettier inside Stylelint here is the link, https://github.com/prettier/stylelint-prettier#recommended-configuration, I hope that this can help you, hasta pronto!, :)
you don't actually have to choose between these tools as they have vastly different purposes. i think its more a matter of understanding how to use them.
while eslint and stylelint are used to notify you about code quality issues, to guide you to write better code, prettier automatically handles code formatting (without notifying me). nothing else.
prettier and eslint both officially discourage using the eslint-plugin-prettier way, as these tools actually do very different things. autofixing with linters on watch isnt a great idea either. auto-fixing should only be done intentionally. you're not alone though, as a lot of devs set this up wrong.
i encourage you to think about what problem you're trying to solve and configure accordingly.
for my teams i set it up like this: - eslint, stylelint, prettier locally installed for cli use and ide support - eslint config prettier (code formatting rules are not eslints business, so dont warn me about it) - vscode workspace config: format on save - separate npm scripts for linting, and formatting - precommit hooks (husky)
so you can easily integrate with gulp. its just js after all ;)
Pros of ESLint
- Consistent javascript - opinions don't matter anymore8
- Free6
- IDE Integration6
- Customizable4
- Focuses code review on quality not style2
- Broad ecosystem of support & users2
Pros of PHPStan
Sign up to add or upvote prosMake informed product decisions
What is ESLint?
What is PHPStan?
Need advice about which tool to choose?Ask the StackShare community!
What companies use PHPStan?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+43