# 🎉 Node-RED Flow Debugger 1.0.0 released

**URL:** <https://discourse.nodered.org/t/node-red-flow-debugger-1-0-0-released/47044>\
**Category:** News\
**Created:** [11 June 2021 15:58 UTC](https://discourse.nodered.org/t/node-red-flow-debugger-1-0-0-released/47044 "2021-06-11T15:58:04Z")\
**Posts on this page:** 10\
**Page:** 2

<div class="post-metadata">

**Author:** ![Paul-Reed](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/paul-reed/32/66906_2.png) [@Paul-Reed](https://discourse.nodered.org/u/Paul-Reed)\
**Post date:** [11 June 2021 20:16 UTC](https://discourse.nodered.org/t/node-red-flow-debugger-1-0-0-released/47044/21 "2021-06-11T20:16:11Z")

</div>

> [@knolleary](#):
>
> I suspect with all your nodes running on timers continually injecting new messages it is overloading the debugger sidebar. Will need to think about how to handle that sort of continual load.

Yes, I'm finding the same.  
Within seconds, the debugger sidebar is awash with data entries from my various flows, making it a little difficult to then navigate.

---

<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:** [11 June 2021 20:17 UTC](https://discourse.nodered.org/t/node-red-flow-debugger-1-0-0-released/47044/22 "2021-06-11T20:17:26Z")

</div>

> [@TotallyInformation](#):
>
> It would be nice to be able to click the breakpoint entries and be taken to the right node in the main editor.

Huh - I thought I implemented that already. But I guess not. I see it does highlight the breakpoint when you hover, just no click action. Added to the list.

---

<div class="post-metadata">

**Author:** ![tree-frog](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/tree-frog/32/89303_2.png) [@tree-frog](https://discourse.nodered.org/u/tree-frog)\
**Post date:** [11 June 2021 20:27 UTC](https://discourse.nodered.org/t/node-red-flow-debugger-1-0-0-released/47044/23 "2021-06-11T20:27:31Z")

</div>

Nick,  
Just a side note then I"m done. I am familiar with Allen Bradley PLC software has a similar Stepping debugging tool in the programming for stepping through the logic scan by scan. It stops all timers since that will trip logic asynchronously and give you false positives. You then must either step or continue. Then your breakpoint is caught again, and then you can inspect your states. I'm trying to explain this, and if I already have please excuse me. It really is a great tool and I appreciate it and all the work that went into it so far.

---

<div class="post-metadata">

**Author:** ![zachowj](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/zachowj/32/37522_2.png) [@zachowj](https://discourse.nodered.org/u/zachowj)\
**Post date:** [11 June 2021 21:19 UTC](https://discourse.nodered.org/t/node-red-flow-debugger-1-0-0-released/47044/24 "2021-06-11T21:19:43Z")

</div>

> [@knolleary](#):
>
> Currently falling down the rabbit hole of discovering why TypeScript changes the case of filenames seemingly randomly. OSX (where I develop) is case insensitive, so I didn't notice.

[https://www.typescriptlang.org/tsconfig#forceConsistentCasingInFileNames](https://www.typescriptlang.org/tsconfig#forceConsistentCasingInFileNames)

---

<div class="post-metadata">

**Author:** ![mtoko](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mtoko/32/138_2.png) [@mtoko](https://discourse.nodered.org/u/mtoko)\
**Post date:** [12 June 2021 06:17 UTC](https://discourse.nodered.org/t/node-red-flow-debugger-1-0-0-released/47044/25 "2021-06-12T06:17:33Z")

</div>

Installed the Flow Debugger and worked out how to use it in a few minutes, so first test passed 😀  
Thanks to Nick and all involved

---

<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:** [12 June 2021 09:48 UTC](https://discourse.nodered.org/t/node-red-flow-debugger-1-0-0-released/47044/26 "2021-06-12T09:48:19Z")

</div>

Fabulous software. Not the kind of software that you come across every day. Really cool...

> [@knolleary](#):
>
> If anyone wants to help contribute with ideas, or better yet, code, then that would be welcome.

Perhaps this is already part of the existing _"edit queue"_ roadmap item, but just to be sure... Beside editing/shifting/removing messages, it would be nice if cloning and inserting would become possible in a far future. That would simplify testing my new nodes, while I have my code debugger open in the background.

---

<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:** [12 June 2021 09:55 UTC](https://discourse.nodered.org/t/node-red-flow-debugger-1-0-0-released/47044/27 "2021-06-12T09:55:50Z")

</div>

> [@BartButenaers](#):
>
> it would be nice if cloning and inserting would become possible in a far future. That would simplify testing my new nodes, while I have my code debugger open in the background

Don't know if it helps you in this instance but have you seen the "inject now" button on the inject node in 2.0.0 beta?

---

<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:** [12 June 2021 10:31 UTC](https://discourse.nodered.org/t/node-red-flow-debugger-1-0-0-released/47044/28 "2021-06-12T10:31:01Z")

</div>

Absolutely. Another feature that I'm going to use a lot 👍

I fact that new Inject-node feature was my trigger to propose a similar feature for the debugger. When I saw that editing messages was already on the debugger roadmap (which seems not easy to me), I thought: if that would ever become possible, then it is also possible to insert a new msg: create a new empty msg object ´{}´ which can be edited using the same editor...

This way you don't have to start adding inject nodes all over the place, you can simply inject it live wherever you want via the debugger...

---

<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:** [12 June 2021 14:33 UTC](https://discourse.nodered.org/t/node-red-flow-debugger-1-0-0-released/47044/29 "2021-06-12T14:33:01Z")

</div>

You might want to avoid accidentally leaving the debugger turned on overnight - It took a couple of minutes for my dev PC to catch up with itself. 🤣 🤣

---

<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:** [11 August 2021 14:33 UTC](https://discourse.nodered.org/t/node-red-flow-debugger-1-0-0-released/47044/30 "2021-08-11T14:33:11Z")

</div>

Closed on 11 August 2021 14:33 UTC

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

[Previous page](https://discourse.nodered.org/t/node-red-flow-debugger-1-0-0-released/47044.md?page=1)
