# Custom node subscribed to flow restart event

**URL:** <https://discourse.nodered.org/t/custom-node-subscribed-to-flow-restart-event/42350>\
**Category:** General\
**Created:** [9 March 2021 15:32 UTC](https://discourse.nodered.org/t/custom-node-subscribed-to-flow-restart-event/42350 "2021-03-09T15:32:37Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![PizzaProgram](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/pizzaprogram/32/19431_2.png) [@PizzaProgram](https://discourse.nodered.org/u/PizzaProgram)\
**Post date:** [13 March 2025 19:03 UTC](https://discourse.nodered.org/t/custom-node-subscribed-to-flow-restart-event/42350/9 "2025-03-13T19:03:22Z")

</div>

## What is the current state / solution for this problem?

- What is the recommended way to develop a node, that has dependencies?
- Is there a (new) way since 2021 that allows to **detect** if a:
  - complete deploy
  - partial deploy
  - flow restart
  - node-red service restart

is happening? And affecting the node itself, or the "child-nodes" which are depending on it?

(More about it [here...](https://discourse.nodered.org/t/node-hierarchy-oppinions/95979))

---

_[View the full topic](https://discourse.nodered.org/t/custom-node-subscribed-to-flow-restart-event/42350)._