Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add historical note to no-typeof-undefined #1992

Merged
merged 4 commits into from
Dec 3, 2022
Merged

Add historical note to no-typeof-undefined #1992

Changes from 2 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
811e0b4
Add historical note to `no-typeof-undefined`
fregante Nov 27, 2022
342a79a
accidentally a word
fregante Nov 27, 2022
74ae360
Drop mention of Strict Mode
fregante Nov 28, 2022
f6037ef
Merge branch 'main' into old-no-typeof-undefined
fregante Dec 3, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/rules/no-typeof-undefined.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,8 @@

Checking if a value is `undefined` by using `typeof value === 'undefined'` is needlessly verbose. It's generally better to compare against `undefined` directly. The only time `typeof` is needed is when a global variable potentially does not exists, in which case, using `globalThis.value === undefined` may be better.

Historical note: Comparing against `undefined` without `typeof` was frowned upon until [strict mode](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Strict_mode) was implemented. This is no longer a problem since strict mode is the default for ES modules.

## Fail

```js
Expand Down