-
Notifications
You must be signed in to change notification settings - Fork 534
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.
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
chore: remove update notifier #2152
Conversation
1254d4f
to
cb76355
Compare
cb76355
to
6b91de7
Compare
@@ -5,7 +5,7 @@ | |||
"pretty": true, | |||
"moduleResolution": "node", | |||
"target": "es2018", | |||
"lib": ["ES2018", "dom"], | |||
"lib": ["ES2018", "ES2019", "dom"], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@maxjeffos Yeah, seen that trick. But it still doesn't make sense that the test is broken only for this PR right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Avishagp, I have theory... I was thinking that since update-notifier
has many deps/transitive deps, along with @types/update-notifier
, probably something in those deps was defining Object.fromEntries
. I think it's quite likely the case.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That totally makes sense. Thanks!
What does this PR do?
Removes the update notification mechanism along with the
update-notifier
dependency.This is a pre-PR to #2105