From the very beginning of using sublime3 to webstrom to vscode, my feelings are as follows:
Sublime loads faster for the first time, and it is a bit troublesome to install plugins each time. The plugins are very rich and easy to use.
The first loading speed of webstrom is extremely slow, especially when there are many modules that webpack depends on.
vscode is recommended by a former colleague, and the project is opened in seconds. It is called the editor with the fastest loading speed, and it is indeed worthy of it.
I remember that when I first came to work in the company, my computer was an old computer with 4G memory. I used sublime at first. It cut the page at the beginning and was compatible with IE6, no problem. Later, I changed it to webstrom and it was fine. Some shortcut keys, feel very cool, quickly find the shortcut keys of the defined method, fold the code, go back to the last cursor position, customize the configuration format code, etc., npm, svn, git are automatically integrated in the software, feel A real artifact.
After that, I used gulp to develop the project and the computer still suffered. After using webpack, the software often crashed and the computer crashed. During this time, I felt that webstrom was really bad. Finally, it was really cool to listen to my colleague's suggestion to switch to vscode, and soon, But it's still uncomfortable to use without as many integrated functions as webstrom.
Finally, I changed a new computer and added 8G memory, and I changed back to webstrom. Because it is very slow to open the software, I will not shut down for a long time. Sometimes I will open many projects at the same time for 1-2 months, and the computer will not be stuck, so I strongly recommend using webstrom. And my projects are always having problems, I can remotely fix bugs at home without having to go to the company in the middle of the night.
The following is my configuration under webstrom with webpack:
Configuration of the vue project:
ES6 node placement:
The custom formatting code configuration is as follows:
It can be configured and most of the same as defined by ESLINT, so that the code formatting can be completed with one click~~~
The eslint file webstrom directly supports it and is placed in the root directory of the file. The configuration is as follows:
In this way, if the code format is not correct, the editor will automatically red line prompts to report errors and make visual modifications. Quickly standardize the code of the team.
When webstrom used the command window npm install to install all the dependent packages for the first time, it sometimes caused the software to crash, because the dependent packages would not be excluded from the first installation.
Every time I create and copy a new project, I will use the git command window to install the dependency package, and then use the webstrom to open the project. If it still gets stuck, I will delete it and start again. This way, there will be fewer problems.