Intermediate
TypeScript
Q70 / 100
What is the effect of "noImplicitAny" compiler option?
Correct! Well done.
Incorrect.
The correct answer is B) It raises an error when a variable or parameter's type cannot be inferred and would default to "any"
B
Correct Answer
It raises an error when a variable or parameter's type cannot be inferred and would default to "any"
Explanation
noImplicitAny forces explicit typing wherever TypeScript would otherwise fall back to the implicit "any" type, improving type safety.
Progress
70/100