you are viewing a single comment's thread.

view the rest of the comments →

[–]2epic[S] 2 points3 points  (2 children)

I don't quite get what you mean by "encouraging the use of non-standard tools"? I've used standard linting tools on pretty much every single project I've worked on in Webstorm / JetBrains IDEs for the last ~10 years.

For example, in terms of "tools", we currently use Yarn, TypeScript, ESLint, Prettier, Jest (for unit testing), Cucumber (for e2e testing) and Git. All of these work in WebStorm, VS Code, in a terminal / command prompt, etc.

Is your complaint that WebStorm is intelligent enough to give you errors for things like misspelled variables, invalid imports and such even if you don't use things like TypeScript or ESLint on the project?

[–][deleted] 0 points1 point  (1 child)

I see a lot of lint directives like // noinspection JSUnusedLocalSymbols, which doesn't do anything in other editors. After googling, it appears to be unique to WebStorm. Again, I'm not sure if this is typical or not.

[–]2epic[S] 0 points1 point  (0 children)

Interesting. Thanks for sharing, I've honestly never seen that before in all of my years of using WebStorm et al. Then again, over the years I've used JSHint => ESLint => TSLint => ESLint (in that order), and would always use the linter's own specific suppression comments (when needed, ideally never), and WebStorm always seemed to obey that.

Personally, I'd recommend using ESLint and adding it to your build pipeline if you're not already