pandaright.blogg.se - Angular webstorm debug

ANGULAR WEBSTORM DEBUG FULL
ANGULAR WEBSTORM DEBUG PRO
ANGULAR WEBSTORM DEBUG CODE

It was a great way to see how the workflow changes depending on the features and toolset provided. Having experimented with different IDE's, I learned about the good and the bad in each. Very basic web dev using online IDEs -> JS dev in a variety of different IDEs -> Settled on VSCode -> optimised VSCode -> learned VIM -> wanted more keyboard control, got a fancy keyboard -> optimised/configured keyboard -> ? -> profit ) I'm probably missing a ton though, my work computer has like ~300 lines in the config JSON, which I expect isn't much compared to some. Utilizing workspace specific color themes - this is a big help if you have a bunch of editors open, it lets you determine which is which at a glance.Hotkeying all of the activity bar items to something memorable, as well as hotkeying show/hide terminal, open file to the side, etc.Disabling the scroll preview/minimap, activity bar, and tabs (I recommend not using tabs and instead relying on the explorer or omnisearch).

ANGULAR WEBSTORM DEBUG PRO

(A good theme doesn't hurt either - I recommend Monokai Pro or Zenburn Dark Matter Lots of aesthetic things, like getting line height right, border padding, fonts, all those sorts of things setup to your preference.Setting autosave to happen after a 1 second delay of inaction.

ANGULAR WEBSTORM DEBUG CODE

Code actions on save- currently I have an auto importer, eslint -fix / prettier running whenever I save a file.I don't have my work computer in front of me (my personal is much less configured) but here are a few things to look for:

One thing I miss from WebStorm was the ease of FTP-style workspaces, though generally cowboy coding is a Bad Thing so it's not really an issue for me anymore, also I'm told VSCode has similar extensions for the same. Maybe my only gripe with VSCode is that it struggles with big projects, anything over 500k LOC and plugins/linters start bugging out.

User land is better for VSCode by an order of magnitude, and I expect that to continue.

ANGULAR WEBSTORM DEBUG FULL

I appreciate that VSCode can painlessly switch between a plain old text editor, and a full fledged IDE. I used to find it tedious to basically have to use a new IDE for each language stack, considering it takes Jetbrains IDEs a lot longer to spin up. Having one editor handle everything is nice for monorepo style projects written in multiple languages.It has much better monorepo support, and I just find its source control easier to use for my day to day workflow. Source Control / Git - probably the biggest feature where I prefer VSCode.Since we're in the microservice meta it's a lot more common to switch between smaller projects. You can customize WebStorm really well too, so this is just preferential, but overall VSCode gives me the vibe of something like Sublime Text rather than an old school IDE like NetBeans. You can customize it to be a lot more minimal. WebStorm fans will regularly rave about this point, but WebStorm is only more capable out of the box with Prettier + ESLint configured properly it's about the same.

Code completion, refactoring, etc, is the same in both with extensions.

Nowadays my language stack is mostly TypeScript, Python, and Rust, (mostly TS) and just having an editor that works exactly how I want for every language is a big deal. I'm a big JetBrains fan, I used to use IntelliJ, PHPStorm, and WebStorm. Try to give it a really fair shake and see if I can learn it better. And this time I think I'm going to try and make myself use it for a while before I rage quit it haha. I'm just hoping that someone out here has a bit of experience moving from webstorm to vs code and can give me some pointers because I'm probably going to try vs code again. The code completion the intellisense the debugging tools all of it. Here's the thing though: as frustrating as web storm is when something like this is broken, when it gets things right (which is like 80 to 90% of the time) it is just amazing. In this case it's the svelte plug-in, it seems to be set to ES4 or something with some of the intellisense errors that I'm getting. Usually my motivation for taking a closer look at vs code is driven by webstorm handling something really terribly. Periodically I take a look at vs code because I keep hearing so much about it and I always believe in giving things a fair shake. I do a significant amount of front end work both at my job and at home and webstorm is my IDE of choice. I've been using webstorm pretty much forever.