ESLint vs PhpStorm

Overview

PhpStorm

Stacks14.3K

Followers11.1K

Votes1.6K

ESLint

Stacks38.6K

Followers14.0K

Votes28

GitHub Stars26.6K

Forks4.8K

ESLint vs PhpStorm: What are the differences?

Introduction

In this Markdown code, we will compare the key differences between ESLint and PhpStorm.

ESLint: ESLint is a linting tool that analyzes JavaScript code for potential errors and enforces coding conventions. It helps developers identify and fix issues in their code before runtime. It is highly customizable and can be integrated with various editors and build systems.
PhpStorm: PhpStorm is an integrated development environment (IDE) specifically built for PHP development. It provides a rich set of features for PHP coding, debugging, and testing. It offers a comprehensive code editor, advanced refactoring tools, and seamless integration with popular frameworks.
ESLint is language-agnostic, while PhpStorm is specific to PHP: ESLint can be used for linting JavaScript code in any project, regardless of the programming language being used. On the other hand, PhpStorm is designed exclusively for PHP development and may not provide the same level of support for other languages.
ESLint focuses on code quality and best practices, while PhpStorm offers a wider range of tools: ESLint primarily focuses on identifying code issues, enforcing coding styles, and promoting best practices. It helps maintain the overall quality of the codebase. PhpStorm, apart from linting, offers features like code completion, debugging, version control integration, and more, making it a comprehensive PHP development environment.
ESLint is highly configurable, while PhpStorm's configuration is IDE-specific: ESLint allows developers to configure almost every aspect of the linting process, from defining custom rules to specifying global variables and environments. PhpStorm, on the other hand, has its own set of configuration options that are specific to the IDE and may not offer the same level of customization as ESLint.
ESLint can be integrated with any code editor, while PhpStorm is its own standalone IDE: ESLint can be integrated with various code editors, including VS Code, Sublime Text, Atom, and more, allowing developers to have consistent linting across different environments. PhpStorm, being an IDE, provides a complete development environment out of the box.

In summary, ESLint is a language-agnostic linting tool focusing on code quality and best practices, while PhpStorm is a feature-rich IDE specifically designed for PHP development. ESLint offers more flexibility in terms of configuration and integration with different editors, while PhpStorm provides a comprehensive set of tools for PHP coding, debugging, and testing within its own standalone IDE.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on PhpStorm, ESLint

Johnny

Software Engineer at StackShare

Aug 15, 2019

Needs adviceon

Visual Studio Code

PhpStorm

WebStorm

When I switched to Visual Studio Code 12 months ago from PhpStorm I was in love, it was great. However after using VS Code for a year, I see myself switching back and forth between WebStorm and VS Code. The VS Code plugins are great however I notice Prettier, auto importing of components and linking to the definitions often break, and I have to restart VS Code multiple times a week and sometimes a day.

We use Ruby here so I do like that Visual Studio Code highlights that for me out of the box, with WebStorm I'd need to probably also install RubyMine and have 2 IDE's going at the same time.

Should I stick with Visual Studio Code, or switch to something else? #help

1.02M views1.02M

Comments

Carlos

Mar 14, 2020

Needs adviceon

Prettier

ESLint

gulp

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.

465k views465k

Comments

Alex

Software Engineer

Aug 7, 2020

Review

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 ;)

159k views159k

Comments

Detailed Comparison

PhpStorm	ESLint
PhpStorm is a PHP IDE which keeps up with latest PHP & web languages trends, integrates a variety of modern tools, and brings even more extensibility with support for major PHP frameworks.	A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. Maintain your code quality with ease.
Smart PHP Code Editor;Code Quality Analysis;Debugging and Testing;HTML/CSS/JavaScript Editor;Cross-platform Experience;Support for all major PHP frameworks;VCS; SQL Editor; Unit Testing;	-
Statistics
GitHub Stars -	GitHub Stars 26.6K
GitHub Forks -	GitHub Forks 4.8K
Stacks 14.3K	Stacks 38.6K
Followers 11.1K	Followers 14.0K
Votes 1.6K	Votes 28
Pros & Cons
Pros 287 Best ide for php 232 Easy to use 218 Functionality 166 Plugins 160 Code analysis Cons 14 Uses a lot of memory 10 Does not open large files 9 Slow 8 Uses Java machine 3 No way to change syntax highlight for files without ext	Pros 8 Consistent javascript - opinions don't matter anymore 6 Free 6 IDE Integration 4 Customizable 2 Broad ecosystem of support & users
Integrations
Vagrant Google App Engine	JavaScript

What are some alternatives to PhpStorm, ESLint?

IntelliJ IDEA

Out of the box, IntelliJ IDEA provides a comprehensive feature set including tools and integrations with the most important modern technologies and frameworks for enterprise and web development with Java, Scala, Groovy and other languages.

Visual Studio

Visual Studio is a suite of component-based software development tools and other technologies for building powerful, high-performance applications.

WebStorm

WebStorm is a lightweight and intelligent IDE for front-end development and server-side JavaScript.

NetBeans IDE

NetBeans IDE is FREE, open source, and has a worldwide community of users and developers.

PyCharm

PyCharm’s smart code editor provides first-class support for Python, JavaScript, CoffeeScript, TypeScript, CSS, popular template languages and more. Take advantage of language-aware code completion, error detection, and on-the-fly code fixes!

Eclipse

Standard Eclipse package suited for Java and plug-in development plus adding new plugins; already includes Git, Marketplace Client, source code and developer documentation. Click here to file a bug against Eclipse Platform.

Android Studio

Android Studio is a new Android development environment based on IntelliJ IDEA. It provides new features and improvements over Eclipse ADT and will be the official Android IDE once it's ready.

RubyMine

JetBrains RubyMine IDE provides a comprehensive Ruby code editor aware of dynamic language specifics and delivers smart coding assistance, intelligent code refactoring and code analysis capabilities.

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.

Codacy

Codacy automates code reviews and monitors code quality on every commit and pull request on more than 40 programming languages reporting back the impact of every commit or PR, issues concerning code style, best practices and security.

Related Comparisons

ESLint vs PhpStorm: What are the differences?

Introduction

In this Markdown code, we will compare the key differences between ESLint and PhpStorm.

ESLint: ESLint is a linting tool that analyzes JavaScript code for potential errors and enforces coding conventions. It helps developers identify and fix issues in their code before runtime. It is highly customizable and can be integrated with various editors and build systems.
PhpStorm: PhpStorm is an integrated development environment (IDE) specifically built for PHP development. It provides a rich set of features for PHP coding, debugging, and testing. It offers a comprehensive code editor, advanced refactoring tools, and seamless integration with popular frameworks.
ESLint is language-agnostic, while PhpStorm is specific to PHP: ESLint can be used for linting JavaScript code in any project, regardless of the programming language being used. On the other hand, PhpStorm is designed exclusively for PHP development and may not provide the same level of support for other languages.
ESLint focuses on code quality and best practices, while PhpStorm offers a wider range of tools: ESLint primarily focuses on identifying code issues, enforcing coding styles, and promoting best practices. It helps maintain the overall quality of the codebase. PhpStorm, apart from linting, offers features like code completion, debugging, version control integration, and more, making it a comprehensive PHP development environment.
ESLint is highly configurable, while PhpStorm's configuration is IDE-specific: ESLint allows developers to configure almost every aspect of the linting process, from defining custom rules to specifying global variables and environments. PhpStorm, on the other hand, has its own set of configuration options that are specific to the IDE and may not offer the same level of customization as ESLint.
ESLint can be integrated with any code editor, while PhpStorm is its own standalone IDE: ESLint can be integrated with various code editors, including VS Code, Sublime Text, Atom, and more, allowing developers to have consistent linting across different environments. PhpStorm, being an IDE, provides a complete development environment out of the box.

ESLint vs PhpStorm

Overview

ESLint vs PhpStorm: What are the differences?