Webstorm is an excellent IDE for web development. It has many useful features to make our lives easier, all of them aiming to automate the repetitive parts of coding. Looking back at my coding speed years ago seems like snail’s pace. The difference is not in my typing speed, but how much I know about the tool I use. Knowing the tool means knowing the features it offers. I’ve collected those features that add the most value to this speedup.

Live Templates

Live templates are useful to insert frequently used code pieces quickly. When you type the abbreviation and hit the tab button, the editor adds the whole template. The template can have placeholders also: they have to be filled out to complete the insertion.

Let’s look at an example. We develop in TDD ( Test Driven Development) and write many tests. Using Mocha and Jasmine as test frameworks, you have to insert describe and it blocks. Typing every character of these blocks is the repetitive way of doing it.

The quick way is to create a live template for the describe block (abbreviation: de).

describe('$TESTGROUP$', function() {
$END$
});

Also, create one for the it block (abbreviation: it).

it('should $TESTCASE$', function() {
$END$
});

The placeholders are started and ended with $ signs. The placeholder $END$ has a special meaning: this is the place of the cursor after the insertion.

Search Everywhere

Searching for text in project files is a common feature in most IDEs, but searching for other things like actions in the menu bar or declarations are rare in other editors. The best thing is that you can search for files, menu actions, and declarations with a single command: just double press the Shift button and start searching everywhere.

Prettier

Prettier is an opinionated code formatter supporting many languages like Javascript, Typescript, CSS, HTML, etc. By using it, you can save time and energy on code formatting.
You can add Prettier to Webstorm through its plugin. To make code formatting automatic, you have to add a file watcher also. This file watcher will listen to save events, and when it occurs, runs Prettier code formatting on the saved file.
If you don’t like automatic code updates, it can be done manually with a keyboard shortcut.

Refactoring

When the code gets messy, or we find duplicate parts, we tend to do refactoring. If the refactored code is used in many places, it can be an error-prone task. Webstorm helps us in this situation with its built-in refactoring capabilities. If the target is a variable, it can be renamed, extracted, inlined, or moved it elsewhere with a single mouse click. The same goes for methods.

Multi-cursor editing

Most of the time, we used to edit the code in one place where the cursor is waiting. There are occasions when we have to do the same editing in different places. The straightforward solution is to edit it in one place, copy it, and paste it to all the locations. The quicker way is to place the cursor to multiple locations by pressing the Alt key (⌥) and clicking the locations. The cursor appears at all the locations where we clicked, and typing happens where the cursors are.

A particular case is when the places we want to edit are in the same column. At this point, we can switch to column selection mode: instead of lines, we can select columns and edit the code inside these columns.

A third multiple-cursor use-case is when we select all the occurrences of the selected text (Edit > Find > Select All Accourences) and the typing/deletion happens everywhere.

Code Navigation

If you use a library and you want to know how that class/function behaves, you have to search and open that file. Webstorm makes this navigation a lot easier. Holding down the Command button (⌘) turns the cursor into definition revealing mode. If you hover an imported class/function, it shows its interface. Clicking the hovered element results in navigating to the definition. You can do the navigation without using the cursor by pressing Command + B. Now you know the definition, but want to go back to the previous place. Webstorm can navigate back to the last edit location (⌘ + ⌥ + ←), making code navigation extremely fast.

Key Promoter

Webstorm has more than 100 shortcuts by default for nearly all the actions and code modifications. Do you know all of them? Well, I don’t. However, the key promoter plugin informs you if you don’t use them. When you do an interaction that you can do with a keyboard shortcut, the plugin tells it in the bottom right corner.

Keyboard Shortcuts

The promoter is a great way to learn the shortcuts for the things you use, but what about those you don’t know? It pays off to read through the list of the shortcuts at least once. I have created a list about those that I find the most useful.

  • Delete line (⌘ + ⌫)
  • Move line up/down (⇧ + ⌥ + ↑ or ↓)
  • Show preferences (⌘ + ,)
  • Duplicate line or selection (⌘ + D)
  • Search everywhere (double ⇧)
  • Expand or shrink selection (⌥ + ↑ or ↓)
  • Column selection mode (⌘ + ⇧ + 8)
  • Find in path (⌘ + ⇧ + F)
  • Replace in path (⌘ + ⇧ + R)
  • Rename definition or variable (⇧ + F6)
  • Go to declaration (⌘ + B, ⌘ + Click)
  • Go to last edit location (⌘ + ⌥ + ← or →)
  • Code completion (⌘ + Space)
  • Multiple cursors (⌥ + Click)
  • Show intentions (⌥ + ⏎)
  • Trigger column selection mode (⌘ + ⇧ + 8)
  • Show intentions (⌥ + ⏎)
  • Comment/uncomment current line/selection (⌘ + /)
  • Reformat code (⌘ + ⌥ + L)
  • Select all occurrences (^ + ⌘ + G)

I have listed the default shortcuts on Mac. You can find the Windows and Linux equivalents on the reference page. They have even shortcut lists where they compare different lists to one another.

Built-in Terminal

Why would you leave the IDE to use the command line if you have one inside it? Webstorm has a built-in terminal that supports multiple sessions, and you can access with a hotkey.

Summary

In this post, we have listed many different features that can speed up development and make you more productive. It is up to you whether you use them or not. The most important thing is to know about them. If you are starting to use a tool, learn about it. If you are developing with it for a while recheck its features in an orderly manner. Because you become more productive by mastering the tools you use.

Originally published at https://dev.to on August 19, 2019.