# Failing to install an updated node

**URL:** <https://discourse.nodered.org/t/failing-to-install-an-updated-node/42994>\
**Category:** General\
**Created:** [22 March 2021 10:50 UTC](https://discourse.nodered.org/t/failing-to-install-an-updated-node/42994 "2021-03-22T10:50:29Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![sander76](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/sander76/32/35508_2.png) [@sander76](https://discourse.nodered.org/u/sander76)\
**Post date:** [22 March 2021 10:50 UTC](https://discourse.nodered.org/t/failing-to-install-an-updated-node/42994/1 "2021-03-22T10:50:29Z")

</div>

I am trying to update a node of mine to the latest version: [node-red-contrib-squidtester (node) - Node-RED](https://flows.nodered.org/node/node-red-contrib-squidtester)

I am now on .13 and want it to become .14. Somehow the palette manager does not come up with an update notification so I am trying to update manually:

From inside my ~/.node-red raspberry pi folder I first do a

`npm list` to confirm my version is indeed .13:

```auto
node-red-project@0.0.1 /home/pi/.node-red
├─┬ node-red-contrib-squidtester@0.0.13
│ ├─┬ js-yaml@4.0.0
│ │ └── argparse@2.0.1
│ └─┬ pretty-ms@7.0.1
│ └── parse-ms@2.1.0

```

Now I enter `npm update node-red-contrib-squidtester`. After the enter it just returns to my prompt without any feedback. But the version is still .13.

If I do `npm show node-red-contrib-squidtester` I get:

```auto

node-red-contrib-squidtester@0.0.14 | MIT | deps: 2 | versions: 12

keywords: node-red, squid

```

So it seems it is able to find a .14 version. But I don't get why I can't update.  
Any suggestions appreciated !

---

<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:** [22 March 2021 11:24 UTC](https://discourse.nodered.org/t/failing-to-install-an-updated-node/42994/2 "2021-03-22T11:24:30Z")

</div>

I see you only published `.14` a short time ago - there is a delay before the catalog used by the palette manager is updated. That said, I can see the catalog does now list the `.14` version.

`npm update ` will update to the latest version of the module that is permitted by its entry in your `package.json` file. That doesn't necessarily mean it will update it to the latest version available generally.

You can run `npm install node-red-contrib-squidtester` to install the latest available version.

---

<div class="post-metadata">

**Author:** ![sander76](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/sander76/32/35508_2.png) [@sander76](https://discourse.nodered.org/u/sander76)\
**Post date:** [22 March 2021 11:44 UTC](https://discourse.nodered.org/t/failing-to-install-an-updated-node/42994/3 "2021-03-22T11:44:07Z")

</div>

I actually did also try and run `npm install node-red-contrib-squidtester`, but without success. I can see there might be a delay between what shows on [npmjs.com](http://npmjs.com) and what I can actually install. Maybe some caching thingy. But I was wondering whether I could "force" an install. But I guess not.

ps. it is updated now.

Thanks !

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [21 May 2021 11:44 UTC](https://discourse.nodered.org/t/failing-to-install-an-updated-node/42994/4 "2021-05-21T11:44:15Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.