Conditional expression with identical branches.Typeof comparing with non-standard value.Suspicious usage of 'bind' with arrow function.Potentially invalid reference to 'this' from closure.Possibly incorrect target of indexed property access.Referencing 'arguments' outside of function.Expression statement which is not assignment or call.Attempt to assign to const or readonly variable.'this' expression which references the global object.You can also set it on a project or a global level.

To enable Code Inspection rules, you can go to Preferences/Settings->Editor->Inspections->Javascript. It's worth noting that this isn't a final list since I have only started using this tool. Some of the rules might be even coverable with ESLint and/or Prettier, but I will list all of them here. You can check all of those over at JetBrains.

Now, there are a whole lot of different checks (and levels of severity) you can set, so I won't be going through them all. It ticked all of my boxes because it was simple, didn't require any installation and had a ton of options. Some Google searches later, I found out about Code Inspections in PhpStorm (as well as WebStorm).

After that, I could proceed with testing different options and having something that could be implemented on a team level. That way I would get the grips with what really makes a difference when checking your complexity. I found out that there are many ways that you could do this, but I was searching for a solution that would be simple to implement. In my opinion, it should prevent you from doing crazy stuff, while maintaining a level of readability. Lately, I've been looking for a simple way to check the complexity of my Javascript code.

Phpstorm javascript