Told me to update, but my version is already the latest one

[gsklee]

More at: raineorshine/npm-check-updates/issues/190

---

IssueHunt Summary

fregante has been rewarded.

Backers (Total: $60.00)

• issuehunt ($60.00)

Submitted pull Requests

• #174 Avoid showing notification if current version is the latest

---

Tips

• Checkout the Issuehunt explorer to discover more funded issues.
• Need some help from other developers? Add your repositories on IssueHunt to raise funds.

---

IssueHunt has been backed by the following sponsors. Become a sponsor

[jokeyrhyme]

A coworker experienced this today. I think using a consuming project multiple times and publishing an update to it in certain sequences (at a particular time of day) can cause this.

[sindresorhus]

I haven't been able to reproduce this, but if anyone submits a failing test, I would be happy to look into it.

[jiripospisil]

Just bumped into this as well. I will look into it some more over the weekend, it's not the first time that's happened to me with various packages.

[kevva]

@jiripospisil, did you install npm@5.0.0-beta.49 with another Node version? If you have two global installs update-notifier doesn't know which one is the current.

[simonua]

This happens to me somewhat frequently. Could it be a timing issue with synchronicity? As in, updating to latest version while a version check is occurring based on the original version in package.json just prior to the update? Maybe there's some sense in suspending the notifier when an install/update is occurring?

We've implemented this in our code, so this has definitely not just been in relation to npm but any update that occurs for one of our packages.

[zkat]

@sindresorhus I'm getting a number of reports about this both on the npm issue tracker, and on twitter.

[krokofant]

Reproduce:

all output

 ~  npm install -g npm-check-updates@2.11.1
/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.11.1
added 2 packages, removed 30 packages and updated 7 packages in 15.162s
 ~  nano ~/.config/configstore/update-notifier-npm-check-updates.json # lower the lastUpdateCheck and save
 ~  ncu -g
⸨░░░░░░░░░░░░░░░░░░⸩ ⠴ :
 aurelia-cli        0.30.0  →  0.30.1
 npm-check-updates  2.11.1  →  2.12.1

 ~  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 30 packages, removed 2 packages and updated 7 packages in 8.044s
 ~  ncu -g


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

⸨░░░░░░░░░░░░░░░░░░⸩ ⠴ :

short version

# 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

Remember to edit the configfile and lower the lastUpdateCheck and save.

[lucasbento]

I had the same issue here, a workaround that solved it is using the callback property and checking the version that's hold on update:

updateNotifier({
  pkg,
  callback: (data, update) => {
    if (!update || pkg.version === update.latest) {
      return;
    }

   console.log(chalk.cyan(
      `There's an update of ${pkg.name} available:`,
      chalk.dim(pkg.version), chalk.reset('→'), chalk.blue(update.latest),
      chalk.dim('\nRun'), chalk.green(chalk.bold(`npm i -g ${pkg.name}`)), chalk.dim('to update.'),
    ));
  },
});

[purplecabbage]

I resolved this using:

       if(notifier.update &&
           notifier.update.latest !== pkg.version) {
            // Notify using the built-in convenience method
            notifier.notify();
        }

[raineorshine]

const updateNotifier = require('update-notifier')
const pkg = require('../package.json')
const notifier = updateNotifier({ pkg })
if (notifier.update && notifier.update.latest !== pkg.version) {
    notifier.notify()
}

[IssueHuntBot]

@IssueHunt has funded $60.00 to this issue.

---

• Submit pull request via IssueHunt to receive this reward.
• Want to contribute? Chip in to this issue via IssueHunt.
• Checkout the IssueHunt Issue Explorer to see more funded issues.
• Need help from developers? Add your repository on IssueHunt to raise funds.

[issuehunt-oss]

@sindresorhus has rewarded $54.00 to @fregante. See it on IssueHunt

• 💰 Total deposit: $60.00
• 🎉 Repository reward(0%): $0.00
• 🔧 Service fee(10%): $6.00