# Not having any luck updating

**URL:** <https://discourse.nodered.org/t/not-having-any-luck-updating/7471>\
**Category:** General\
**Created:** [1 February 2019 11:30 UTC](https://discourse.nodered.org/t/not-having-any-luck-updating/7471 "2019-02-01T11:30:03Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [1 February 2019 11:30 UTC](https://discourse.nodered.org/t/not-having-any-luck-updating/7471/1 "2019-02-01T11:30:03Z")

</div>

This is getting very frustrating.

I seem to be going in circles.

RPI 2B.

```auto
Raspberry Pi Model B Rev 2

PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)"
NAME="Raspbian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

Raspberry Pi reference 2018-03-13
Generated using pi-gen, https://github.com/RPi-Distro/pi-gen, 00013d7972122d1304aacda8fff5098f073ceb43, stage5

```

NR 0.19.5  
NPM....

```auto
pi@TimePi:~ $ npm version
^C
pi@TimePi:~ $ npm
^C
pi@TimePi:~ $ npm --help
^C
pi@TimePi:~ $ npm ?
^C
pi@TimePi:~ $ 

```

(edited part)  
man npm:

```auto
NPM(1) NPM(1)

NAME
       npm - javascript package manager

SYNOPSIS
         npm <command> [args]

VERSION
       6.4.1

```

Dashboard 2.13.2  
(This has only just happened and I don't really know how it happened. It took multiple attempts and it somehow just - finally - worked.)

I have about 5 nodes I want to update.

This is an example of one:

```auto
pi@TimePi:~/.node-red $ npm install node-red-contrib-simple-message-queue
npm WARN node-red-project@0.0.1 No repository field.
npm WARN node-red-project@0.0.1 No license field.

+ node-red-contrib-simple-message-queue@0.0.2
updated 1 package and audited 875 packages in 769.108s
found 6 low severity vulnerabilities
  run `npm audit fix` to fix them, or `npm audit` for details
pi@TimePi:~/.node-red $ sudo systemctl restart nodered

```

So you can see I restarted Node-Red.

Went back to GUI/web page.

`simple-message-queue version 0.0.2 update to 0.2.2`

This is just beyond frustrating.

One of my other RPI's is quite happy. Don't know why or how.  
It has been turned off more than it has been on recently.

This one is on 24/7.

The NUC is also pretty happy. Though it has a bit more grunt that the poor Pi.

What ever.

Please, someone.  
Explain to me what is going on.

I am jumping through the hoops. Not worrying about the messages when I update from the terminal - as from the web page it just doesn't do anything.  
It just (repeatedly) says it is updated and isn't after a restart.

So: all things being equal and doing what I was told; it should update.  
Alas no one told it that.

---

<div class="post-metadata">

**Author:** ![ukmoose](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ukmoose/32/13_2.png) [@ukmoose](https://discourse.nodered.org/u/ukmoose)\
**Post date:** [1 February 2019 11:34 UTC](https://discourse.nodered.org/t/not-having-any-luck-updating/7471/2 "2019-02-01T11:34:29Z")

</div>

Try `npm cache clean` and then try again

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [1 February 2019 11:42 UTC](https://discourse.nodered.org/t/not-having-any-luck-updating/7471/3 "2019-02-01T11:42:54Z")

</div>

Getting this:

```auto
pi@TimePi:~ $ npm cache clean
npm ERR! As of npm@5, the npm cache self-heals from corruption issues and data extracted from the cache is guaranteed to be valid. If you want to make sure everything is consistent, use 'npm cache verify' instead. On the other hand, if you're debugging an issue with the installer, you can use `npm install --cache /tmp/empty-cache` to use a temporary cache instead of nuking the actual one.
npm ERR! 
npm ERR! If you're sure you want to delete the entire cache, rerun this command with --force.

npm ERR! A complete log of this run can be found in:
npm ERR! /home/pi/.npm/_logs/2019-02-01T11_42_16_305Z-debug.log
pi@TimePi:~ $ 

```

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [1 February 2019 11:45 UTC](https://discourse.nodered.org/t/not-having-any-luck-updating/7471/4 "2019-02-01T11:45:38Z")

</div>

This is the log file mentioned. (Sorry)

```auto
pi@TimePi:~ $ cd .npm/_logs
pi@TimePi:~/.npm/_logs $ cat 2019-02-01T11_42_16_305Z-debug.log 
0 info it worked if it ends with ok
1 verbose cli ['/usr/bin/node', '/usr/bin/npm', 'cache', 'clean']
2 info using npm@6.4.1
3 info using node@v8.12.0
4 verbose config Skipping project config: /home/pi/.npmrc. (matches userconfig)
5 verbose npm-session 33646676b4a09f7c
6 verbose stack Error: As of npm@5, the npm cache self-heals from corruption issues and data extracted from the cache is guaranteed to be valid. If you want to make sure everything is consistent, use 'npm cache verify' instead. On the other hand, if you're debugging an issue with the installer, you can use `npm install --cache /tmp/empty-cache` to use a temporary cache instead of nuking the actual one.
6 verbose stack
6 verbose stack If you're sure you want to delete the entire cache, rerun this command with --force.
6 verbose stack at clean (/usr/lib/node_modules/npm/lib/cache.js:72:22)
6 verbose stack at EventEmitter.cache (/usr/lib/node_modules/npm/lib/cache.js:47:16)
6 verbose stack at Object.commandCache.(anonymous function) (/usr/lib/node_modules/npm/lib/npm.js:159:13)
6 verbose stack at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/bin/npm-cli.js:131:30)
6 verbose stack at _combinedTickCallback (internal/process/next_tick.js:132:7)
6 verbose stack at process._tickCallback (internal/process/next_tick.js:181:9)
7 verbose cwd /home/pi
8 verbose Linux 4.14.79+
9 verbose argv "/usr/bin/node" "/usr/bin/npm" "cache" "clean"
10 verbose node v8.12.0
11 verbose npm v6.4.1
12 error As of npm@5, the npm cache self-heals from corruption issues and data extracted from the cache is guaranteed to be valid. If you want to make sure everything is consistent, use 'npm cache verify' instead. On the other hand, if you're debugging an issue with the installer, you can use `npm install --cache /tmp/empty-cache` to use a temporary cache instead of nuking the actual one.
12 error
12 error If you're sure you want to delete the entire cache, rerun this command with --force.
13 verbose exit [1, true]
pi@TimePi:~/.npm/_logs $ 

```

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [1 February 2019 11:51 UTC](https://discourse.nodered.org/t/not-having-any-luck-updating/7471/5 "2019-02-01T11:51:02Z")

</div>

(Yeah, I know.....)

Now - on said RPI - I notice that `big-timer` has upated to 2.1.1 which it wasn't before.

ARGH!

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [1 February 2019 12:33 UTC](https://discourse.nodered.org/t/not-having-any-luck-updating/7471/6 "2019-02-01T12:33:09Z")

</div>

> [@Trying\_to\_learn](#):
>
> pi@TimePi:~ $ npm version

`npm --version`

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [1 February 2019 12:37 UTC](https://discourse.nodered.org/t/not-having-any-luck-updating/7471/7 "2019-02-01T12:37:05Z")

</div>

```auto
pi@TimePi:~/.node-red $ npm --version
6.4.1
pi@TimePi:~/.node-red $ 

```

But I did get it from the `man npm` post above:

```auto
(edited part)
man npm:

NPM(1) NPM(1)

NAME
       npm - javascript package manager

SYNOPSIS
         npm <command> [args]

VERSION
       6.4.1

```

---

<div class="post-metadata">

**Author:** ![zenofmud](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/zenofmud/32/316_2.png) [@zenofmud](https://discourse.nodered.org/u/zenofmud)\
**Post date:** [1 February 2019 12:38 UTC](https://discourse.nodered.org/t/not-having-any-luck-updating/7471/8 "2019-02-01T12:38:01Z")

</div>

see [Updates - node-red-contrib-bigtimer - HELP](https://discourse.nodered.org/t/updates-node-red-contrib-bigtimer-help/7475/2) it was just updated

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [1 February 2019 12:40 UTC](https://discourse.nodered.org/t/not-having-any-luck-updating/7471/9 "2019-02-01T12:40:53Z")

</div>

Thanks Zenofmud.

I do hope it works, but really - from where I am standing - this applies to ALL nodes.

Not just bigtimer.

That is just one of many which need updating.

Somehow in this mess, the dashboard did get updated.

(But on an aside: the ui\_LED still doesn't. I see the icon, but I inject `true` and `!true` into it and it just stays grey. But on another machine it changes colour.)

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [1 February 2019 12:52 UTC](https://discourse.nodered.org/t/not-having-any-luck-updating/7471/10 "2019-02-01T12:52:41Z")

</div>

> [@Trying\_to\_learn](#):
>
> rerun this command with --force

As it says, `npm cache clean --force`

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [1 February 2019 12:54 UTC](https://discourse.nodered.org/t/not-having-any-luck-updating/7471/11 "2019-02-01T12:54:50Z")

</div>

Oh, please....

Ok, but I read

> [@ukmoose](#):
>
> Try `npm cache clean` and then try again

The `--force` isn't really there.  
If it was needed, I say it should be specified.  
(No offence UKM)

But I didn't know if it was simply for information gathering or it was needing to be done, so I did what was said.

Shall try with `--force` and report back.

Oh, "red flag" for me - kind of.

So, `npm`..... `sudo` or not?  
And from which directory? Is it important?  
Home,  
Node-red  
npm?

---

<div class="post-metadata">

**Author:** ![ukmoose](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ukmoose/32/13_2.png) [@ukmoose](https://discourse.nodered.org/u/ukmoose)\
**Post date:** [1 February 2019 12:59 UTC](https://discourse.nodered.org/t/not-having-any-luck-updating/7471/12 "2019-02-01T12:59:56Z")

</div>

the "`---force`" depends on your version of npm

Good luck with solving your problems

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [1 February 2019 13:02 UTC](https://discourse.nodered.org/t/not-having-any-luck-updating/7471/13 "2019-02-01T13:02:09Z")

</div>

> [@ukmoose](#):
>
> the " `---force` " depends on your version of npm

That's fair enough. I get that.

I wasn't having a go at you for posting that.

I didn't understand that it was implied.

I did the command and posted the result.  
If it needed the `--force` at that stage, then I was waiting for confirmation.

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [1 February 2019 13:07 UTC](https://discourse.nodered.org/t/not-having-any-luck-updating/7471/14 "2019-02-01T13:07:53Z")

</div>

This is the latest stuff I see:

```auto
pi@TimePi:~/.node-red $ npm cache clean --force
npm WARN using --force I sure hope you know what you are doing.
pi@TimePi:~/.node-red $ npm install node-red-contrib-cpu
npm WARN node-red-project@0.0.1 No repository field.
npm WARN node-red-project@0.0.1 No license field.

+ node-red-contrib-cpu@0.0.2
updated 1 package and audited 875 packages in 230.033s
found 6 low severity vulnerabilities
  run `npm audit fix` to fix them, or `npm audit` for details
pi@TimePi:~/.node-red $ sudo systemctl restart nodered
pi@TimePi:~/.node-red $ 

```

Node-red restarted.

still version 0.0.2

```auto
node-red-contrib-cpu
0.0.2

```

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [1 February 2019 13:10 UTC](https://discourse.nodered.org/t/not-having-any-luck-updating/7471/15 "2019-02-01T13:10:46Z")

</div>

@Trying_to_learn

Looking at the output you provided at the start:

```auto
pi@TimePi:~/.node-red $ npm install node-red-contrib-simple-message-queue
npm WARN node-red-project@0.0.1 No repository field.
npm WARN node-red-project@0.0.1 No license field.

+ node-red-contrib-simple-message-queue@0.0.2

```

Note how it reports it has installed version 0.0.2 at the end there - that is odd given 0.2.2 is the latest available.

With the version of npm you have (ie, pretty much the latest 6.x), it should _not_ be necessary to clean the cache. It _should_ still be checking with the npm repository to check what the latest is.

Please can you try running:

```auto
~/.node-red $ npm install node-red-contrib-simple-message-queue@0.2.2

```

Note the `@0.2.2` at the end.

Please then provide:

1. the output of that command.
2. what `~/.node-red/node_modules/node-red-contrib-simple-message-queue/package.json` says its `version` is

Right now, I _cannot_ explain why this Pi is behaving like this. Right now I'm focussed on trying to help you get it upgraded.

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [1 February 2019 13:12 UTC](https://discourse.nodered.org/t/not-having-any-luck-updating/7471/16 "2019-02-01T13:12:56Z")

</div>

> [@Trying\_to\_learn](#):
>
> That is just one of many which need updating.
> 
> Somehow in this mess, the dashboard did get updated.

I think that a deep breath is required. Maybe take a step back for a second and think about a process that will help you rather than frustrate.

It may help if I explain how I do things.

I don't generally update nodes from within the admin ui. I update from npm and npm has a very convenient couple of commands that lets you update everything with minimal effort.

```auto
# Tell me what needs updating
npm outdated
# Update everything that needs updating
npm update

```

To make it even easier, I make use of the `package.json` file that lives in the userDir folder (normally `~/.node-red` and npm's ability to define and run "scripts". So I can do `npm run update` and everything is updated.

Below is an example of amended from one of my package.json files. Just note that my start command is for temporarily running node-red manually, I wouldn't normally use that since it is started by systemd on the Pi. Also note that the start command would need adjusting for you anyway since I don't use the standard installation. If you are interested, you can see how and why I do it differently [here](https://github.com/TotallyInformation/alternate-node-red-installer).

```json
{
  "name": "node-red-nrlive",
  "description": "A Node-RED Project on Pi3",
  "version": "0.19.2",
  "license": "MIT",
  "author": "Julian Knight",
  "repository": {},
  "scripts": {
    "start": "/usr/local/bin/node --max-old-space-size=128 ../node_modules/node-red/red.js --userDir ../.data",
    "restart": "sudo systemctl restart nodered",
    "check": "npm outdated",
    "update": "npm update",
    "logs": "sudo journalctl -u nodered -e -f -n 50",
    "admin": "node-red-admin "
  },
  "dependencies": {
    "node-red-contrib-bigtimer": "^2.0.8",
    "node-red-contrib-blockly": "^1.1.0",
    "node-red-contrib-google-home-notify": "*",
    "node-red-contrib-influxdb": "~0.2.2",
    "node-red-contrib-later": "*",
    "node-red-contrib-moment": "^3.0.1",
    "node-red-contrib-rfxcom": "^2.6.3",
    "node-red-contrib-rive": "~1.1.0",
    "node-red-contrib-smartplug": "*",
    "node-red-contrib-syslog-input": "^1.0.1",
    "node-red-contrib-telegrambot": "^4.8.0",
    "node-red-contrib-throttle": "~0.1.6",
    "node-red-contrib-time-range-switch": "*",
    "node-red-contrib-uibuilder": "^1.0.12",
    "node-red-dashboard": "^2.13.0",
    "node-red-node-darksky": "~0.1.18",
    "node-red-node-openweathermap": "^0.2.1",
    "node-red-node-ping": "0.0.16",
    "node-red-node-rbe": "^0.2.4",
    "node-red-node-serialport": "*",
    "node-red-node-smooth": "*",
    "node-red-node-sqlite": "^0.3.6",
    "node-red-node-weather-underground": "*"
  },
  "engines": {
    "node": "8.*"
  }
}

```

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [1 February 2019 13:15 UTC](https://discourse.nodered.org/t/not-having-any-luck-updating/7471/17 "2019-02-01T13:15:59Z")

</div>

Ok Nick.

I shall try to go through your questions and answer them all to the best of my knowledge:

> [@knolleary](#):
>
> Note how it reports it has installed version 0.0.2 at the end there - that is odd given 0.2.2 is the latest available.

Correct.

I see that 0.2.2 is available.

 ![Screenshot%20from%202019-02-02%2000-12-40](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/5/5b974b086650e2d5adcc0f25f27fda7109a6032d.png)

I have tried to update it multiple times. It just will not update.

> [@knolleary](#):
>
> With the version of npm you have (ie, pretty much the latest 6.x), it should _not_ be necessary to clean the cache. It _should_ still be checking with the npm repository to check what the latest is.

> [@Trying\_to\_learn](#):
>
> pi@TimePi:~/.node-red $ npm --version 6.4.1 pi@TimePi:~/.node-red $

Doing that now. Shall post this reply only to keep information flowing.

Shall post update when it happens.

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [1 February 2019 13:16 UTC](https://discourse.nodered.org/t/not-having-any-luck-updating/7471/18 "2019-02-01T13:16:15Z")

</div>

> [@Trying\_to\_learn](#):
>
> The `--force` isn't really there.  
> If it was needed, I say it should be specified.  
> (No offence UKM)
> 
> But I didn't know if it was simply for information gathering or it was needing to be done, so I did what was said.
> 
> Shall try with `--force` and report back.
> 
> Oh, "red flag" for me - kind of.
> 
> So, `npm` ..... `sudo` or not?  
> And from which directory? Is it important?  
> Home,  
> Node-red  
> npm?

As I went through previously - **not** `sudo` to clean the local cache, `sudo` to clean the global cache.

This is a recent change to npm which is why the standard command no longer works as it did before but it tells you why and what.

Node.js and npm are still evolving very rapidly so issues like this are expected. Other languages such as PERL or Python are available to people who are averse to change 😄

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [1 February 2019 13:21 UTC](https://discourse.nodered.org/t/not-having-any-luck-updating/7471/19 "2019-02-01T13:21:33Z")

</div>

> [@knolleary](#):
>
> Right now, I _cannot_ explain why this Pi is behaving like this. Right now I'm focussed on trying to help you get it upgraded.

You should run `npm outdated` as the first port of call for issues like this. Later versions of npm have a nasty tendency to enforce semantic versioning and therefore it doesn't like to install what you might think is obvious.

Here is an example:

```bash
pi@pi3:~/nrlive/.data $ npm outdated
Package Current Wanted Latest Location
node-red-contrib-bigtimer 2.0.8 2.1.3 2.1.3 node-red-nrlive
node-red-contrib-telegrambot 4.8.0 4.8.0 5.1.5 node-red-nrlive
node-red-dashboard 2.13.0 2.13.2 2.13.2 node-red-nrlive
pi@pi3:~/nrlive/.data $

```

Note that the "Wanted" column might not have the same version as the "Latest" and if that is the case, it is because of the `dependencies` list in your `package.json` having been set by npm and it preventing the installation of a newer version because it may have "breaking changes". npm forces you to think about that and to amend the `package.json` file or to deliberately install the newer version using the version override that Nick as already shown.

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [1 February 2019 13:22 UTC](https://discourse.nodered.org/t/not-having-any-luck-updating/7471/20 "2019-02-01T13:22:13Z")

</div>

> [@TotallyInformation](#):
>
> ```auto
> # Tell me what needs updating
> npm outdated
> # Update everything that needs updating
> npm update
> 
> ```
> 
> To make it even easier, I make use of the `package.json` file that lives in the userDir folder (normally `~/.node-red` and npm's ability to define and run "scripts". So I can do `npm run update` and everything is updated.

While I am waiting for the other thing to complete:

I'm confused.  
You have:  
`npm update`  
But then you have:  
`npm run update` and everything is updated.

Which is it?

Sorry. I can't resolve the confusion.

[Next page](https://discourse.nodered.org/t/not-having-any-luck-updating/7471.md?page=2)