* When I'm working in a JavaScript or TypeScript file in WebStorm, when I reference something that is not currently imported (eg. * Related to the previous bullet, debugging and stepping through code (either the running app, or when in testing) seems a lot easier to configure, more consistent and more reliable in WebStorm It's also more consistent in WebStorm vs VS Code, since separate testing plugins in VS Code means that going from a project using one test runner (Jest) to a project running another (eg. * I like WebStorm's support and built-in GUI for running unit tests a lot more than the Jest plugins I've tried for VS Code. * file nesting works great in WebStorm, but is missing in VS Code: For example, here are a few off the top of my head: Nothing really proprietary there.īut some of the more subtle, built-in features of WebStorm I just find missing or in some way lacking in VS Code. 2 spaces instead of tabs) are configured automatically. editorconfig files, as many editors do, so our standards (eg. WebStorm has support for eslint, I think it even works out of the box if I remember correctly. I ended up using both IDEA and VSCode for different things: IDEA as an IDE when I need to work with projects for more than an hour, and VSCode when I just want to quickly edit a file, use the live share or remote editing.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |