For the last five or so years, I’ve been using Jetbrains Rider as my primary IDE for C# work, and Webstorm for any Javascript, Typescript, and NodeJS work.

Since Rider has most of the Webstorm features built in, along with Datagrip features, and much more, it initially seemed perfect to consolidate all my work into Rider, since my work is a fairly even mix of C#, Typescript, and Javascript.

For C#, Rider is fantastic.

However for Javascript and Typescript, Rider is mostly great, but with some key annoyances that aren’t present in Webstorm.

The most glaring example of a deficiency in Rider that is not present in Webstorm is:

After removing or renaming a JS/TS a file, you'll need to manually update references, which is very painful in a large refactor! And this isn't a new problem; the problem has existed over five years now. There are no known workarounds, and Jetbrains hasn't provided a timeline for a fix.

Take a look at the comments on these tickets:

Some recommendations:

  • Use Webstorm if you mainly work with Typescript/Javascript, and only do light C# work. Consider a different editor such Visual Studio code for any light C# work.
  • Use Rider if you mainly do C# work, and only do light Typescript/Javascript work.
  • Use both Webstorm and Rider if you do substantial C# and Typescript/Javascript work, to avoid Rider’s limitations when working with JS/TS files.

Thanks for reading!

Enjoyed this article? Follow me on Twitter for more like this.

Do you have any questions, feedback, or anything that you think I’d be interested in? Please leave a comment below, or get in touch with me directly.