# Node-RED Breakpoints

**URL:** <https://discourse.nodered.org/t/node-red-breakpoints/2073>\
**Category:** Feature Requests\
**Created:** [5 August 2018 17:40 UTC](https://discourse.nodered.org/t/node-red-breakpoints/2073 "2018-08-05T17:40:47Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![machadotiago](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/machadotiago/32/23776_2.png) [@machadotiago](https://discourse.nodered.org/u/machadotiago)\
**Post date:** [5 August 2018 17:40 UTC](https://discourse.nodered.org/t/node-red-breakpoints/2073/1 "2018-08-05T17:40:47Z")

</div>

Hello everyone,  
I was talking with a friend about how we can improve the debugging process of developing a Flow using Node-RED and he came with the idea of having breakpoints like the ones we have in the most famous IDEs.  
Wouldn't be nice to have such a thing? Specially if we could manipulate the msg during a break event.

---

<div class="post-metadata">

**Author:** ![BartButenaers](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bartbutenaers/32/10476_2.png) [@BartButenaers](https://discourse.nodered.org/u/BartButenaers)\
**Post date:** [5 August 2018 19:00 UTC](https://discourse.nodered.org/t/node-red-breakpoints/2073/2 "2018-08-05T19:00:46Z")

</div>

Hi Tiago,

I think this is already on the long-term planning. See this [Trello](https://trello.com/c/MUEGnF6h/68-flow-debugger) item.

Kind regards,  
Bart Butenaers

---

<div class="post-metadata">

**Author:** ![loldiges](https://avatars.discourse-cdn.com/v4/letter/l/6a8cbe/32.png) [@loldiges](https://discourse.nodered.org/u/loldiges)\
**Post date:** [22 August 2018 10:48 UTC](https://discourse.nodered.org/t/node-red-breakpoints/2073/3 "2018-08-22T10:48:24Z")

</div>

Hi,

although not exactly what you want, this may help you until the mentioned Trello item is implemented:

At our company when developing new nodes or extending existing nodes we debug somehow like this:

- [https://github.com/Microsoft/vscode-recipes/tree/master/nodemon](https://github.com/Microsoft/vscode-recipes/tree/master/nodemon)

- Instead of "attach" I use the following launch.json:

- find the files of the nodes you are using, open them (or the folder) in vscode.

- add Breakpoints

- now when pressing the green arrow for debugging node-red will start via nodemon

- happy debugging

Best regards  
Lars

---

<div class="post-metadata">

**Author:** ![fangzhu](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/fangzhu/32/5796_2.png) [@fangzhu](https://discourse.nodered.org/u/fangzhu)\
**Post date:** [11 June 2019 03:16 UTC](https://discourse.nodered.org/t/node-red-breakpoints/2073/4 "2019-06-11T03:16:02Z")

</div>

I wonder if this flow debugger made into the next release.

---

<div class="post-metadata">

**Author:** ![BartButenaers](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bartbutenaers/32/10476_2.png) [@BartButenaers](https://discourse.nodered.org/u/BartButenaers)\
**Post date:** [11 June 2019 05:02 UTC](https://discourse.nodered.org/t/node-red-breakpoints/2073/5 "2019-06-11T05:02:33Z")

</div>

Hi @fangzhu,  
As you can see [here](https://discourse.nodered.org/t/accelerating-the-journey-to-1-0/9815) the **Pluggable Message Routing** is still on the roadmap, but not in the 1.0 release. Moreover when that feature ever becomes available, I assume somebody still has to develop some kind of Node-RED debugger on (using the pluggable message routing)?  
Bart

---

<div class="post-metadata">

**Author:** ![fangzhu](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/fangzhu/32/5796_2.png) [@fangzhu](https://discourse.nodered.org/u/fangzhu)\
**Post date:** [11 June 2019 05:30 UTC](https://discourse.nodered.org/t/node-red-breakpoints/2073/6 "2019-06-11T05:30:10Z")

</div>

Thanks for quick response.

What I wanted is more like a break point that can temporary stop the flow process at some node so that developer can confirm the intermediate result, such as context data, database data at that point etc.

I am looking forward to this wonderful feature in the future.

---

<div class="post-metadata">

**Author:** ![AlonAmiraabluedragon](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/alonamiraabluedragon/32/24155_2.png) [@AlonAmiraabluedragon](https://discourse.nodered.org/u/AlonAmiraabluedragon)\
**Post date:** [20 June 2020 05:45 UTC](https://discourse.nodered.org/t/node-red-breakpoints/2073/7 "2020-06-20T05:45:31Z")

</div>

@fangzhu  
A little something I've made to simulate breakpoints on Node-RED nodes.  
Very alpha stage, but works for my needs.  
[node-red-contrib-msg-tracer](https://gitlab.com/monogoto.io/node-red-contrib-msg-tracer)

---

<div class="post-metadata">

**Author:** ![BartButenaers](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bartbutenaers/32/10476_2.png) [@BartButenaers](https://discourse.nodered.org/u/BartButenaers)\
**Post date:** [20 June 2020 06:37 UTC](https://discourse.nodered.org/t/node-red-breakpoints/2073/8 "2020-06-20T06:37:49Z")

</div>

Hi Alon (@AlonAmiraabluedragon),  
Welcome to the forum!  
I had already made some advertisement for your node some time ago:

> [@A new node that fascinates me](https://discourse.nodered.org/t/a-new-node-that-fascinates-me/24117):
>
> Hi folks, From time to time I discover a new node that draws my attention. I discovered last week the [node-red-contrib-msg-tracer](https://gitlab.com/monogoto.io/node-red-contrib-msg-tracer) node, which I find very fascinating ... Reason for my interest: a couple of years ago I wanted to develop a flow debugger node. However there was already a [flow debugger](https://trello.com/c/MUEGnF6h/68-flow-debugger) item on the trello whiteboard, and a old stale [debugger branch](https://github.com/node-red/node-red/tree/debugger) on Github. Therefore I have never started developing, because it seemed to me that this was destined to become core functionality (i…

I'm very impressed by your work!!!

---

<div class="post-metadata">

**Author:** ![AlonAmiraabluedragon](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/alonamiraabluedragon/32/24155_2.png) [@AlonAmiraabluedragon](https://discourse.nodered.org/u/AlonAmiraabluedragon)\
**Post date:** [21 June 2020 08:00 UTC](https://discourse.nodered.org/t/node-red-breakpoints/2073/9 "2020-06-21T08:00:19Z")

</div>

Thanks, I hope you find it useful!  
Though I have to admit @knolleary was right in his comment, I did end up using private APIs and "dirty" tricks as mentioned, I verified compatibility with Node-RED 0.20 -\> 1.0  
but the ability to debug, having "breakpoints", step-by-step, was something I missed greatly while having to maintain complex flows, so for me it's still better than nothing.

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [21 June 2020 08:28 UTC](https://discourse.nodered.org/t/node-red-breakpoints/2073/10 "2020-06-21T08:28:26Z")

</div>

Hi @AlonAmiraabluedragon perhaps if you are still interested, you could discuss with Nick & Dave & come to an agreement on implementation then you could contribute to core?

It would take a load off these 2 guys (who I can only imagine are overloaded with the breakneck pace of development) - then everyone would benefit from your contribution by it being built in to core.

Would be good to see such a prominent feature take shape.

---

<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:** [21 June 2020 08:42 UTC](https://discourse.nodered.org/t/node-red-breakpoints/2073/11 "2020-06-21T08:42:55Z")

</div>

A flow debugger is on the roadmap.

It is top of the list once we get the pluggable message router feature in. Doing anything before that would be premature.

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [21 June 2020 08:58 UTC](https://discourse.nodered.org/t/node-red-breakpoints/2073/12 "2020-06-21T08:58:39Z")

</div>

Absolutely Nick however I don't think I was clear & you might not have caught my inference. I was inferring the op could assist in the overall solution (including the message routing). As you said in the other thread, a missed opportunity that could bring effort directed at helping deliver the backlog.

Just trying to help & not meaning to step on any toes.