Silent Errors
JavaScript can fail siently.
A silent error will not stop your program. The execution will continue.
The reason for silent errors is historical:
The first version of JavaScript did not have catch...try exceptions.
Note: Silent errors are issues that do not throw exceptions or stop execution, but still cause logic bugs, unexpected behavior, or failures that are easy to miss.
Below are some examples of common silent errors, with examples to try:
Example
let x = 1 / 0;
Example
let result = "Not Active.";
let isActive = false;
// ❌ Assignment, not comparison
if (isActive = true) {
let result = "Active!";
}
Explanation
When execution reaches the if statement, you might expect that the conditional block will not be executed because isActive is false.
But, the code (isActive = true) in the evaluation will set isActive to true instead of checking equality with (isActive == true).
This (true) is also the value of the if condition, so the block will be executed.
Note: The above mistake is not an error that JavaScript could have detected (it may have been intended). It is a mistake of the programmer.
Example
// NaN - no error, just wrong data
const result = parseInt("abc");
Example
const user = {};
let result = user.name;
Type Coercion
Type coercion is the automatic (implicit) conversion of values from one data type to another.
Because JavaScript is weakly typed, it doesn't throw errors when types don't match; it just tries to coerce them.
JavaScript coerces types differently per operator, so type coercion can hide bugs.
Example
let result1 = ('5' + '2'); // = 52
let result2 = ('5' - '2'); // = 3
String Coercion (+)
If any part of a + operation is a string, JavaScript converts everything to strings:
let x = "5" + 2 // x = "52"
Numeric Coercion
Other arithmetic operators (-, *, /, %) and the unary plus (+x) force values into numbers.
let x = "5" - 2 // x = 3
Loose Equality (==)
This operator performs coercion to find a "common type" before comparing.
let x = (5 == "5") // x = true
Practices to Avoid Bugs
Use === (Strict Equality) This checks both value and type without coercion, preventing weird results.
Be Explicit Instead of relying on automatic behavior, use MDN's recommended conversion methods like Number() or String() to make your intent clear.
Watch for NaN If a string cannot be converted to a valid number, like "abc" - 1), the result is NaN (Not-a-Number).
Note: See Also: JavaScript Errors JavaScript Error Statemets JavaScript Error Object JavaScript Debugging
