What is WebStorm?
Who uses WebStorm?
Why developers like WebStorm?
Here are some stack decisions, common use cases and reviews by companies and developers who chose WebStorm in their tech stack.
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.
Working on a project recently, wanted an easy modern frontend to work with, decoupled from our backend. To get things going quickly, decided to go with React, Redux.js, redux-saga, Bootstrap.
On the backend side, Go is a personal favourite, and wanted to minimize server overheads so went with a #serverless architecture leveraging AWS Lambda, AWS CloudFormation, Amazon DynamoDB, etc.
For IDE/tooling I tend to stick to the #JetBrains tools: WebStorm / Goland.
Obviously using Git, with GitLab private repo's for managing code/issues/etc.
For all our team's coding because of its support of core libraries like angular and ruby on rails WebStorm
- Support for React and Angular
- Integration with build tools, linters and test runners
- UI for working with Git and other VCS including a visual merge tool