Skip to content

Commit 7e4ccd2

Browse files
author
Dave Conway-Jones
committed
fixup upgrade doc to only mention cache flush for node.js upgrades
1 parent ca4eb6a commit 7e4ccd2

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

docs/getting-started/upgrading.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,6 @@ on a Raspberry Pi, please refer to <a href="/docs/hardware/raspberrypi">these in
1010
If you have installed Node-RED as a global npm package, you can upgrade to the
1111
latest version with the following commands:
1212

13-
sudo npm cache clean
1413
sudo npm install -g --unsafe-perm node-red
1514

1615
To check for, and re-install outdated nodes that are installed in the user directory you have two options:
@@ -29,10 +28,10 @@ You will then need to stop and restart Node-RED.
2928

3029
## Upgrading Node.js
3130

32-
If you upgrade Node.js, for example from v4.x to v6.x, it is better to stop
31+
If you upgrade Node.js, for example from v4.x to v8.x, it is better to stop
3332
Node-RED, and then re-install as follows:
3433

35-
sudo npm cache clean
34+
sudo npm cache clean --force
3635
sudo npm install -g --unsafe-perm node-red
3736

3837
You will also need to rebuild any nodes that have binary dependancies. If you

0 commit comments

Comments
 (0)