How do null and undefined affect type coercion?

Can you explain how null and undefined affect type coercion in JavaScript?

Sure! In JavaScript, both null and undefined are special values that can affect type coercion. Null represents the intentional absence of any object value, while undefined means a variable has been declared but not assigned a value.

What happens when you use null or undefined in a comparison?

When comparing null and undefined using ==, they are considered equal. However, using === will show that they are not the same type, so they won't be equal.

Can you give an example of type coercion with these values?

Absolutely! For example, if you do null + 1, it results in 1 because null is coerced to 0. But undefined + 1 results in NaN because undefined cannot be coerced to a number.

Are there any best practices for using null and undefined?

Yes! It's generally a good practice to use null for intentional absence of value and reserve undefined for uninitialized variables. This helps maintain clarity in your code.