# Node-RED restart require every time when i install updated version of my Nodes

**URL:** <https://discourse.nodered.org/t/node-red-restart-require-every-time-when-i-install-updated-version-of-my-nodes/75521>\
**Category:** Developing Nodes\
**Created:** [21 February 2023 17:41 UTC](https://discourse.nodered.org/t/node-red-restart-require-every-time-when-i-install-updated-version-of-my-nodes/75521 "2023-02-21T17:41:59Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![raweee](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/raweee/32/14768_2.png) [@raweee](https://discourse.nodered.org/u/raweee)\
**Post date:** [21 February 2023 17:42 UTC](https://discourse.nodered.org/t/node-red-restart-require-every-time-when-i-install-updated-version-of-my-nodes/75521/1 "2023-02-21T17:42:00Z")

</div>

Hi,  
I'm new in Node-RED' Nodes development, I have created a set of nodes to perform some specific tasks, These Nodes require continuous modifications and updates.

But whenever i install update of my Nodes in Node-RED, Node-RED force me to restart the Node-RED. I can see that the update is not required by other Nodes in Node-RED, That mean i'm doing something wrong.

Can anyone please explain(if possible) how it works.  
Thanks in advance.

---

<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:** [21 February 2023 18:17 UTC](https://discourse.nodered.org/t/node-red-restart-require-every-time-when-i-install-updated-version-of-my-nodes/75521/2 "2023-02-21T18:17:21Z")

</div>

When developing, it is easiest to work on a local copy of node-red. You can then install your developing nodes using:

```auto
cd ~/.node-red
npm install /path/to/your/dev/code/

```

But you still need to restart node-red to pick up the latest changes to the .js file. You can simplify this by using something like PM2 with its watch feature - simply watch for changes to any key files and force a restart.

Hope this helps.

---

<div class="post-metadata">

**Author:** ![raweee](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/raweee/32/14768_2.png) [@raweee](https://discourse.nodered.org/u/raweee)\
**Post date:** [21 February 2023 19:33 UTC](https://discourse.nodered.org/t/node-red-restart-require-every-time-when-i-install-updated-version-of-my-nodes/75521/3 "2023-02-21T19:33:27Z")

</div>

Hello,  
Thanks @TotallyInformation for your valuable and fast reply, using PM2 will also helps me in creating Nodes better.  
But, I think i'm not able to explain my question correctly.

Actually, My Nodes are already published on npm and i'm installing my updated node from Node-RED' pattels manager. When install was complete, Node-RED force me to restart(in my case).

While updating other nodes (like dashboard and other good nodes) restart is not forced, Nodes simply get updated.

Am I missing something or third party nodes require restart. (Sorry for dump question)

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [21 February 2023 19:46 UTC](https://discourse.nodered.org/t/node-red-restart-require-every-time-when-i-install-updated-version-of-my-nodes/75521/4 "2023-02-21T19:46:43Z")

</div>

What dependencies have you got in the node that does this?

---

<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:** [21 February 2023 21:07 UTC](https://discourse.nodered.org/t/node-red-restart-require-every-time-when-i-install-updated-version-of-my-nodes/75521/5 "2023-02-21T21:07:39Z")

</div>

> [@raweee](#):
>
> When install was complete, Node-RED force me to restart(in my case).

Ah, I see. Odd. I've never worked out what causes that myself. Not had it happen on one of my nodes but I've certainly seen it happen.

---

<div class="post-metadata">

**Author:** ![Falfango](https://avatars.discourse-cdn.com/v4/letter/f/5e9695/32.png) [@Falfango](https://discourse.nodered.org/u/Falfango)\
**Post date:** [22 February 2023 09:42 UTC](https://discourse.nodered.org/t/node-red-restart-require-every-time-when-i-install-updated-version-of-my-nodes/75521/6 "2023-02-22T09:42:57Z")

</div>

My experience. After installing a new node, no restart is needed. But updating any node Node-RED requires a restart. This is also true for dashboard.

---

<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:** [23 April 2023 09:43 UTC](https://discourse.nodered.org/t/node-red-restart-require-every-time-when-i-install-updated-version-of-my-nodes/75521/7 "2023-04-23T09:43:13Z")

</div>

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