Skip to content
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.

cli: shinier update-notifier #20122

Closed
wants to merge 1 commit into from
Closed

cli: shinier update-notifier #20122

wants to merge 1 commit into from

Conversation

zkat
Copy link
Contributor

@zkat zkat commented Mar 21, 2018

This message is based on the one pnpm uses, which
I think takes care of all the false update messages and
missing -g that happens with the default notifier message.

Preview:
screen shot 2018-03-21 at 12 21 46

I did 4 things:

  1. Moved the update check to post-npm.load() so we have access to config. I think this is fine -- if your npm isn't even loading, you can't even update, so.
  2. Added a colorful message about what "level" the update is (major/minor/patch)
  3. Added a link to the changelog right in the message
  4. Forced a -g in the message because update-notifier's detection of globals keeps messing up and if people have npm installed locally, they probably know well enough that they need to omit the -g -- vs folks getting confused because the -g is missing.

Cheers to @zkochan for the corresponding version of this in pnpm, which I think is way better than the default, and I hope he's ok with us cribbing it like this. 💚

@zkat zkat requested a review from a team as a code owner March 21, 2018 12:22
@iarna iarna force-pushed the release-next branch 3 times, most recently from bcc4670 to 4a65b3b Compare March 23, 2018 21:22
@zkat zkat force-pushed the zkat/shiny-notifier branch 3 times, most recently from 719cb2e to 001fd3d Compare April 5, 2018 17:29
This message is based on the one pnpm uses, which
I think takes care of all the false update messages and
missing -g that happens with the default notifier message.

It also tells people what "level" the update is.
iarna pushed a commit that referenced this pull request Apr 9, 2018
This message is based on the one pnpm uses, which
I think takes care of all the false update messages and
missing -g that happens with the default notifier message.

It also tells people what "level" the update is.

Credit: @zkat
PR-URL: #20122
Reviewed-By: @iarna
iarna pushed a commit that referenced this pull request Apr 10, 2018
This message is based on the one pnpm uses, which
I think takes care of all the false update messages and
missing -g that happens with the default notifier message.

It also tells people what "level" the update is.

Credit: @zkat
PR-URL: #20122
Reviewed-By: @iarna
iarna pushed a commit that referenced this pull request Apr 10, 2018
This message is based on the one pnpm uses, which
I think takes care of all the false update messages and
missing -g that happens with the default notifier message.

It also tells people what "level" the update is.

Credit: @zkat
PR-URL: #20122
Reviewed-By: @iarna
iarna pushed a commit that referenced this pull request Apr 10, 2018
This message is based on the one pnpm uses, which
I think takes care of all the false update messages and
missing -g that happens with the default notifier message.

It also tells people what "level" the update is.

Credit: @zkat
PR-URL: #20122
Reviewed-By: @iarna
iarna pushed a commit that referenced this pull request Apr 11, 2018
This message is based on the one pnpm uses, which
I think takes care of all the false update messages and
missing -g that happens with the default notifier message.

It also tells people what "level" the update is.

Credit: @zkat
PR-URL: #20122
Reviewed-By: @iarna
iarna pushed a commit that referenced this pull request Apr 11, 2018
This message is based on the one pnpm uses, which
I think takes care of all the false update messages and
missing -g that happens with the default notifier message.

It also tells people what "level" the update is.

Credit: @zkat
PR-URL: #20122
Reviewed-By: @iarna
@iarna iarna force-pushed the release-next branch 3 times, most recently from 2e76172 to fe31e66 Compare April 13, 2018 20:20
@iarna iarna force-pushed the release-next branch 2 times, most recently from 63c9452 to 1b021d0 Compare April 21, 2018 00:09
@iarna
Copy link
Contributor

iarna commented May 3, 2018

Landed in 6.0.0!

@iarna iarna closed this May 3, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants