# 🎉 Node-RED 3.0.0-beta.2 released

**URL:** <https://discourse.nodered.org/t/node-red-3-0-0-beta-2-released/62698>\
**Category:** News\
**Created:** [16 May 2022 14:15 UTC](https://discourse.nodered.org/t/node-red-3-0-0-beta-2-released/62698 "2022-05-16T14:15:29Z")\
**Posts on this page:** 20\
**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:** [17 May 2022 09:34 UTC](https://discourse.nodered.org/t/node-red-3-0-0-beta-2-released/62698/21 "2022-05-17T09:34:57Z")

</div>

> [@shrickus](#):
>
> the swipe is crossing right at the point where 2 wires cross

I don't think so, if you look at the dashed swipe track line, you'll see I curved it's path between the 2 crossed lines, but yes, maybe it was a little close.  
I think that the bigger problem is trying to perform a 'consistent speed' swipe using a touchpad, whilst holding down a touchpad button, and the keyboard combination at the same time. It isn't easy! and results in wires being missed because the cursor travelled too fast over a particular section of the swipe.  
But, not a big problem, lets leave it here, just need to be aware and double check afterwards, and if it's missed a wire, I can always Ctl-Z and try again 😀

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [17 May 2022 09:40 UTC](https://discourse.nodered.org/t/node-red-3-0-0-beta-2-released/62698/22 "2022-05-17T09:40:22Z")

</div>

> [@Paul-Reed](#):
>
> maybe it was a little close.

the width of the wires is actually wider than the visible width in order to make them easier to select in normal operation

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/4/f/4f97fbc941cc4baf2eeaef63a1d0a0e9d5061730.png)

---

<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:** [17 May 2022 11:12 UTC](https://discourse.nodered.org/t/node-red-3-0-0-beta-2-released/62698/23 "2022-05-17T11:12:46Z")

</div>

I think that it is about as good as it gets right now and the main thing is to make sure that the documentation mentions this.

---

<div class="post-metadata">

**Author:** ![Flachmann](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/flachmann/32/60457_2.png) [@Flachmann](https://discourse.nodered.org/u/Flachmann)\
**Post date:** [19 May 2022 09:43 UTC](https://discourse.nodered.org/t/node-red-3-0-0-beta-2-released/62698/24 "2022-05-19T09:43:48Z")

</div>

I tried Node-RED 3 beta and want to let you know some thoughts.

Node-RED 3 now automatically create dummy names, e.g. "function 1", or "link in 2". But this clashes with the nrLint plugin checks 'no-unnamed-functions' and 'no-unnamed-links'. The linter doesn't detect these nodes as being unnamed.

I think that these automatic names are not very helpful at all, that is why the linter was such a great tool to identify unnamed functions. Automatic names are nice for temporary debug nodes, but not functions or links.

Or, nrLint must count these dummy names as being unnamed.

---

<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:** [19 May 2022 09:49 UTC](https://discourse.nodered.org/t/node-red-3-0-0-beta-2-released/62698/25 "2022-05-19T09:49:53Z")

</div>

> [@Flachmann](#):
>
> The linter doesn't detect these nodes as being unnamed.

That was partly the intention.

> [@Flachmann](#):
>
> I think that these automatic names are not very helpful at all

It was designed to reduce the places where a flow has mostly unnamed items making debugging less difficult. Why not simply name them as you go?

---

<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:** [19 May 2022 09:56 UTC](https://discourse.nodered.org/t/node-red-3-0-0-beta-2-released/62698/26 "2022-05-19T09:56:08Z")

</div>

> [@Flachmann](#):
>
> I think that these automatic names are not very helpful at all

But they are better than no name as they are at least unique within your flows.

We could certainly add an option to the rules to flag nodes that still have a default name set - but it would be an option that could be toggled, rather than fixed behaviour.

---

<div class="post-metadata">

**Author:** ![Flachmann](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/flachmann/32/60457_2.png) [@Flachmann](https://discourse.nodered.org/u/Flachmann)\
**Post date:** [19 May 2022 10:13 UTC](https://discourse.nodered.org/t/node-red-3-0-0-beta-2-released/62698/27 "2022-05-19T10:13:38Z")

</div>

Yes, that's exactly what I usually do. 😉 But hey, in the heat of the moment some nodes get overlooked, or naming is delayed. If you concentrate on what the flow should do, there is often not the right time to think about good function names.

Once the flow works I usually look over it and name functions etc. This is where the linter is great help.

---

<div class="post-metadata">

**Author:** ![Flachmann](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/flachmann/32/60457_2.png) [@Flachmann](https://discourse.nodered.org/u/Flachmann)\
**Post date:** [19 May 2022 10:16 UTC](https://discourse.nodered.org/t/node-red-3-0-0-beta-2-released/62698/28 "2022-05-19T10:16:40Z")

</div>

Yes, Nick, great idea. At least the linter should be able to determine unnamed nodes. If not it would make a mockery of it.

---

<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:** [19 May 2022 10:41 UTC](https://discourse.nodered.org/t/node-red-3-0-0-beta-2-released/62698/29 "2022-05-19T10:41:45Z")

</div>

@Flachmann would you be kind enough to add an issue for this item on the main node-red repo so it is not missed? Please link back to this thread for reference. Ta.

---

<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:** [19 May 2022 15:46 UTC](https://discourse.nodered.org/t/node-red-3-0-0-beta-2-released/62698/31 "2022-05-19T15:46:04Z")

</div>

Split this topic on 19 May 2022 15:46 UTC

A post was split to a new topic: [Shortcuts for Monaco editor](https://discourse.nodered.org/t/shortcuts-for-monaco-editor/62855)

---

<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:** [21 May 2022 01:11 UTC](https://discourse.nodered.org/t/node-red-3-0-0-beta-2-released/62698/32 "2022-05-21T01:11:38Z")

</div>

What am I doing wrong? This is on Firefox and Chromium. Alt key, OK, then left mouse button and move the mouse pointer over the wires. This is getting the gripper and the whole browser window is moving.

---

<div class="post-metadata">

**Author:** ![LosinIt](https://avatars.discourse-cdn.com/v4/letter/l/439d5e/32.png) [@LosinIt](https://discourse.nodered.org/u/LosinIt)\
**Post date:** [21 May 2022 03:57 UTC](https://discourse.nodered.org/t/node-red-3-0-0-beta-2-released/62698/33 "2022-05-21T03:57:46Z")

</div>

Are you holding the Alt key down until you finish moving the mouse?

---

<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 May 2022 06:27 UTC](https://discourse.nodered.org/t/node-red-3-0-0-beta-2-released/62698/34 "2022-05-21T06:27:12Z")

</div>

> [@tree-frog](#):
>
> This is getting the gripper and the whole browser window is moving.

What OS is that on?

If there's an OS level handler for that particular combination, then it will be preventing it from reaching the browser.... and we'll need to have another think about the choice of shortcut

---

<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 May 2022 06:56 UTC](https://discourse.nodered.org/t/node-red-3-0-0-beta-2-released/62698/35 "2022-05-21T06:56:36Z")

</div>

Morning Nick. When I was first working on the mouse and modifier design doc, I had it down as control drag but because we handle **mouse down** instead of **click** for **quick add** , there was a race condition. That's why, on my first attempt at remapping, I moved the quick add handler to **mouse up** but there were too many quirks and code paths and everything I did to handle that quirk led to another quirk. That's when I changed to the alt key as that was unused. If we intend on revisiting this, we might want to consider giving it another go using **control** and **control shift** instead of the alt key?

---

<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:** [21 May 2022 19:46 UTC](https://discourse.nodered.org/t/node-red-3-0-0-beta-2-released/62698/36 "2022-05-21T19:46:54Z")

</div>

Linux Mint 20.3 Una

---

<div class="post-metadata">

**Author:** ![cymplecy](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cymplecy/32/2773_2.png) [@cymplecy](https://discourse.nodered.org/u/cymplecy)\
**Post date:** [21 May 2022 19:58 UTC](https://discourse.nodered.org/t/node-red-3-0-0-beta-2-released/62698/37 "2022-05-21T19:58:39Z")

</div>

Could it not be just a node that's dragged out of the sidebar like all the others and avoid all this trouble?

---

<div class="post-metadata">

**Author:** ![ghayne](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ghayne/32/39_2.png) [@ghayne](https://discourse.nodered.org/u/ghayne)\
**Post date:** [21 May 2022 20:38 UTC](https://discourse.nodered.org/t/node-red-3-0-0-beta-2-released/62698/38 "2022-05-21T20:38:51Z")

</div>

> [@knolleary](#):
>
> If there's an OS level handler for that particular combination, then it will be preventing it from reaching the browser.... and we'll need to have another think about the choice of shortcut

Yep, on MX Linux I had to disable the default ALT drag shortcut to get wire slicing working!

---

<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:** [21 May 2022 22:09 UTC](https://discourse.nodered.org/t/node-red-3-0-0-beta-2-released/62698/39 "2022-05-21T22:09:25Z")

</div>

Why not combine it with Link Node In/Out. Upon selection just check option to make it a junction.

---

<div class="post-metadata">

**Author:** ![Jleagle](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/jleagle/32/55636_2.png) [@Jleagle](https://discourse.nodered.org/u/Jleagle)\
**Post date:** [21 May 2022 23:05 UTC](https://discourse.nodered.org/t/node-red-3-0-0-beta-2-released/62698/40 "2022-05-21T23:05:05Z")

</div>

Is upgrading with docker as simple as changing the tag from 2-\>3? or does anything else need doing?

---

<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 May 2022 23:08 UTC](https://discourse.nodered.org/t/node-red-3-0-0-beta-2-released/62698/41 "2022-05-21T23:08:06Z")

</div>

As this is a beta release, you need to use the node-red-dev images - [🎉 Node-RED 3.0.0-beta.2 released - #14 by hardillb](https://discourse.nodered.org/t/node-red-3-0-0-beta-2-released/62698/14)

[Previous page](https://discourse.nodered.org/t/node-red-3-0-0-beta-2-released/62698.md?page=1)

[Next page](https://discourse.nodered.org/t/node-red-3-0-0-beta-2-released/62698.md?page=3)