Equality operator may cause type coercion

Reports a usage of an equality operator that may cause unexpected type coercions. Suggests replacing == and != with type-safe equality operators === and !==.

Depending on the option selected, one of the following cases will be reported:

All usages of == and != operators.
All usages except comparison with null. Some code styles allow using x == null as a replacement for x === null || x === undefined.
Only suspicious expressions, such as: == or != comparisons with 0, '', null, true, false, or undefined.

Locating this inspection

By ID

Can be used to locate inspection in e.g. Qodana configuration files, where you can quickly enable or disable it, or adjust its settings.

-Equalitycomparisonwithcoercionjs

Via Settings dialog

Path to the inspection settings via IntelliJ Platform IDE Settings dialog, when you need to adjust inspection settings directly from your IDE.

Settings or Preferences | Editor | Inspections | JavaScript and TypeScript | Probable bugs

Inspection ID: JSEqualityComparisonWithCoercion

Inspection options

Here you can find the description of settings available for the Equality operator may cause type coercion inspection, and the reference of their default values.

Highlight usages of '==' and '!='

Option ID:

mySeverity

Default value:

All except when comparing with null or typeof

Other available settings:

All
Only suspicious expressions

Suppressing Inspection

You can suppress this inspection by placing the following comment marker before the code fragment where you no longer want messages from this inspection to appear:

//noinspection -Equalitycomparisonwithcoercionjs

More detailed instructions as well as other ways and options that you have can be found in the product documentation:

Inspection Details
By default bundled with:
Can be installed with plugin:	JavaScript and TypeScript, 253.31890.0

Last modified: 04 March 2026