Newly updated ncu informs of update

[krokofant]

• I have read the list of known issues before filing this issue.
• I have searched for similiar issues before filing this issue.

• node version: v8.1.2
• npm version: 5.0.4
• npm-check-updates version: 2.12.1

---

I often react to a newly updated ncu reporting that the just installed updated is available to update to. I find it hard to replicate but this has come to my mind before so I thought I'd share the issue.

[raineorshine]

Thanks for bring it to our attention. Hopefully someone can find a way to consistently reproduce.

Will you post a full output next time it happens to you? That will help me understand it more precisely. I wasn't clear in your description whether you were talking about an update for ncu itself or one of your dependencies.

[krokofant]

@raineorshine It's when ncu itself is updated. The update available banner is what this issue is about.

Example output:

✘  ~  npm install -g npm-check-updates
/usr/local/bin/npm-check-updates -> /usr/local/lib/node_modules/npm-check-updates/bin/npm-check-updates
/usr/local/bin/ncu -> /usr/local/lib/node_modules/npm-check-updates/bin/ncu
+ npm-check-updates@2.12.1
added 45 packages, removed 3 packages and updated 20 packages in 16.285s
 ~  ncu -g


   ╭──────────────────────────────────────────────╮
   │                                              │
   │      Update available 2.11.3 → 2.12.1        │
   │   Run npm i -g npm-check-updates to update   │
   │                                              │
   ╰──────────────────────────────────────────────╯

Next time ncu is run it does not report about the update.

---

I tried to reproduce this be installing an older version and checking npm -gbut then I didn't get the update banner. What in the code regulates when the update banner is displayed? It does not seem to display all the times.

[raineorshine]

That's really strange. That is from a drop-in module that should work out of the box. Hard to investigate since it involves a version upgrade.

…

On Tue, Jun 27, 2017 at 11:01 AM krokofant ***@***.***> wrote: @raineorshine <https://github.com/raineorshine> It's when ncu itself is updated. Example output: ✘  ~  npm install -g npm-check-updates /usr/local/bin/npm-check-updates -> /usr/local/lib/node_modules/npm-check-updates/bin/npm-check-updates /usr/local/bin/ncu -> /usr/local/lib/node_modules/npm-check-updates/bin/ncu + ***@***.*** added 45 packages, removed 3 packages and updated 20 packages in 16.285s ~  ncu -g ╭──────────────────────────────────────────────╮ │ │ │ Update available 2.11.3 → 2.12.1 │ │ Run npm i -g npm-check-updates to update │ │ │ ╰──────────────────────────────────────────────╯ Next time ncu is run it does not report about the update. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#372 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAtyxPdRo7rf7jk84WujYD14ECVpNo1Rks5sITWAgaJpZM4OGkpx> .

[krokofant]

I found the issue upstream yeoman/update-notifier#67

And an older local issue linked via that thread #190

Could we leave this issue open until it's resolved upstream?

Edit: I reproduced the issue with this

# install old npm-check-updates
npm install -g npm-check-updates@2.11.1
# reset the lastUpdate time
sed -i '' -E "s/([0-9]+)/0/" ~/.config/configstore/update-notifier-npm-check-updates.json
# make ncu check for updates once
ncu -g
# install latest
npm install -g npm-check-updates
# what's this now?
ncu -g

[raineorshine]

Good find!!! Thank you! I will watch that issue closely.

…

On Wed, Jun 28, 2017 at 4:37 AM krokofant ***@***.***> wrote: I found the issue upstream yeoman/update-notifier#67 <yeoman/update-notifier#67> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#372 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAtyxCwvtjkMczP79Au6LpXxG860HiRMks5sIizygaJpZM4OGkpx> .