# How to get the update prompt in the palette manager for privately published npm node

**URL:** https://discourse.nodered.org/t/how-to-get-the-update-prompt-in-the-palette-manager-for-privately-published-npm-node/89515
**Category:** Developing Nodes
**Created:** [15 July 2024 11:21 UTC](https://discourse.nodered.org/t/how-to-get-the-update-prompt-in-the-palette-manager-for-privately-published-npm-node/89515 "2024-07-15T11:21:41Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![IoTGreenbelt](https://avatars.discourse-cdn.com/v4/letter/i/e495f1/32.png) [@IoTGreenbelt](https://discourse.nodered.org/u/IoTGreenbelt)
#### Post date: [15 July 2024 11:21 UTC](https://discourse.nodered.org/t/how-to-get-the-update-prompt-in-the-palette-manager-for-privately-published-npm-node/89515/1 "2024-07-15T11:21:41Z")

</div>

I have a privately published node that is updated correctly with the new version on npm, however I'm unable to update it via the palette manager 'update' button.

I've gone through the publish instructions but still not able to see the update button.

How would I go about getting node-red to look for new versions of a private npm node?

Thanks

---

<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: [15 July 2024 13:46 UTC](https://discourse.nodered.org/t/how-to-get-the-update-prompt-in-the-palette-manager-for-privately-published-npm-node/89515/2 "2024-07-15T13:46:29Z")

</div>

Hi @IoTGreenbelt

The palette manager uses the catalog published by [flows.nodered.org](http://flows.nodered.org) to know when there are updates available.

If your custom node is not in the public catalogue, then Node-RED won't know about any updates you publish.

One option would be to create your own catalogue (a URL that serves a JSON object) which you can configure Node-RED to use via it's settings file in addition to the community catalog.

Can share more pointers if that's a path you're interested in.

---

<div class="post-metadata">

### Author: ![IoTGreenbelt](https://avatars.discourse-cdn.com/v4/letter/i/e495f1/32.png) [@IoTGreenbelt](https://discourse.nodered.org/u/IoTGreenbelt)
#### Post date: [15 July 2024 14:27 UTC](https://discourse.nodered.org/t/how-to-get-the-update-prompt-in-the-palette-manager-for-privately-published-npm-node/89515/3 "2024-07-15T14:27:34Z")

</div>

Thanks for the prompt response,

Yes please, I'd be curious to know what's involved in setting up a catalogue

---

<div class="post-metadata">

### Author: ![IoTGreenbelt](https://avatars.discourse-cdn.com/v4/letter/i/e495f1/32.png) [@IoTGreenbelt](https://discourse.nodered.org/u/IoTGreenbelt)
#### Post date: [19 July 2024 12:54 UTC](https://discourse.nodered.org/t/how-to-get-the-update-prompt-in-the-palette-manager-for-privately-published-npm-node/89515/4 "2024-07-19T12:54:58Z")

</div>

Resolved, followed [this](https://github.com/node-red/node-red/wiki/Design%3A-Palette-Management-UI#customising-the-catalog) to create the catalogue, served from an Azure static web app and then added CORS headers as the last step.

---

<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: [2 August 2024 12:55 UTC](https://discourse.nodered.org/t/how-to-get-the-update-prompt-in-the-palette-manager-for-privately-published-npm-node/89515/5 "2024-08-02T12:55:24Z")

</div>

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