Rule Change: (valid-typeof) undefined should be banned

[Zzzen]

What rule do you want to change?

valid-typeof

What change to do you want to make?

Generate more warnings

How do you think the change should be implemented?

A new default behavior

Example code

typeof foo === null
typeof foo === undefined

What does the rule currently do for this code?

only null is reported

What will the rule do after it's changed?

both null and undefined should be reported

Participation

• I am willing to submit a pull request to implement this change.

Additional comments

No response

[mdjermanovic]

This was partially discussed in #14074.

I think it makes sense to report global undefined regardless of requireStringLiteralsoption. It's a small change in the functionality of this rule that would catch probably the most common mistakes with typeof.

I'll champion this.

(As a future enhancement and a much bigger change in the functionality, this rule could use getStaticValue. That would catch global undefined since it evaluates to the undefined value, and more).

[nzakas]

This change makes sense.