Issue with WebStorm with "esModuleInterop": true about typescript-node-starter

[bowdenk7]

Are you able to specify which version of TypeScript that WebStorm uses to compile? Seems like they don't have support for 2.7?

[mattwelke]

I was setting WebStorm to use the TypeScript compiler in my project, which was 2.7.2. Their website claims that it supports 2.7, but they actually had this bug I'm referring to logged about a month or two ago. So it looks like this is a bug in WebStorm right now which is hopefully somewhere on their road map to fix.

A workaround is to just go back to the old style of importing CommonJS modules.

[bowdenk7]

Might work if you give their latest Release Candidate a shot.

Just curious, is there anything in particular that makes you choose WebStorm, or is it just personal preference?

[mattwelke]

Stronger Intellisense in some situations, refactoring tools etc. Though I haven't committed to using WebStorm over free tools. I was just exploring it. Right now, friction like that was enough to turn me off. I find with Visual Studio Code, I feel less pressure to do things "the JetBrains way". WebStorm wanted me to arrange my build process according to their liking, complaining if files to run after the build aren't there yet (duh, I haven't built yet) and so I'm sticking with Visual Studio Code for now, which seems to break things down into smaller steps that I can manually perform (do a build, then do a run, etc).

[bowdenk7]

Thanks for the details! Always interesting to hear about other people's experiences with different tools.

[vimkin]

Disabling checkbox "Also for projects without tsconfig.json" in Settings > Languages & Frameworks > Typescript seems to help.

[peterblazejewicz]

for reference, original issues was related to WebStorm, see their blog post comments:
https://blog.jetbrains.com/webstorm/2016/03/how-to-compile-typescript-in-webstorm/#comment-315741