# 🎉 Node-RED 1.1.0-beta.1 released

**URL:** <https://discourse.nodered.org/t/node-red-1-1-0-beta-1-released/27761>\
**Category:** News\
**Created:** [4 June 2020 10:38 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-1-released/27761 "2020-06-04T10:38:31Z")\
**Posts on this page:** 20\
**Page:** 4

<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:** [6 June 2020 11:37 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-1-released/27761/62 "2020-06-06T11:37:48Z")

</div>

Hi, I have found if you open the help sometimes its not populated until you click another tab

 ![rede-red-v1.1.0](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/b/1/b160b6d832e174c337ae57dcc569db0a699ccb4d.gif)

#### Steps to re-produce...

- close sidebar
- refresh browser
- use `CTRL+SPACE` or action list "show help tab" or `RED.sidebar.help.show()` or `RED.sidebar.show("help")` to
- click debug tab button or context

Additionally this happens with the info panel too

#### Another observation

- if I ALT-TAB to another window, the info panel populates (redraws?)  
 ![rede-red-v1.1.0b](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/b/2/b211468ed23fecf00b4c234e1baf6eea09ecf9d9.gif)

#### NOTES

- Windows 10 2004 build
- Latest chrome
- node-red latest V1.1.0 (running from source - including all recent merges)

#### LASTLY

- is `SHIFT+?` supposed to open the shortcuts?

#### EDIT...

- the ALT-TAB thing happens in Edge too (so not chrome related)
- the no help thing also happens in Edge

---

<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:** [6 June 2020 11:42 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-1-released/27761/63 "2020-06-06T11:42:26Z")

</div>

> [@Hypnos](#):
>
> I may be wrong, but should the usage changed to the new way without the dash?

You win the prize for the "I wonder who will notice that" bug.

---

<div class="post-metadata">

**Author:** ![ristomatti](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ristomatti/32/5857_2.png) [@ristomatti](https://discourse.nodered.org/u/ristomatti)\
**Post date:** [6 June 2020 12:16 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-1-released/27761/64 "2020-06-06T12:16:51Z")

</div>

> [@Steve-Mcl](#):
>
> #### LASTLY
> 
> - is `SHIFT+?` supposed to open the shortcuts?

That'd be a strange default as in many keyboards you'll need to press shift to get a question mark.

---

<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:** [6 June 2020 12:40 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-1-released/27761/65 "2020-06-06T12:40:05Z")

</div>

Nick / Dave,

I notice nodes now permit `\n` new lines.

I didn't notice this in the change log so its either a nice side effect or you forgot to mention it?

V1.0.6...  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/4/3/4327f93eb0be9130c7dd3ac678deaa1cf2901cba.png)

V1.1.0...  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/1/f/1f8c1711e902924867794f6bf4ba906a3ec8bc51.png)

---

<div class="post-metadata">

**Author:** ![ristomatti](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ristomatti/32/5857_2.png) [@ristomatti](https://discourse.nodered.org/u/ristomatti)\
**Post date:** [6 June 2020 12:42 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-1-released/27761/66 "2020-06-06T12:42:36Z")

</div>

> [@Steve-Mcl](#):
>
> notice nodes now permit `\n` new lines.
> 
> I didn't notice this in the change log so its either a nice side affect or you forgot to mention it?

I believe this was in the full change list. (didn't double check though)

---

<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:** [6 June 2020 12:44 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-1-released/27761/67 "2020-06-06T12:44:10Z")

</div>

> [@ristomatti](#):
>
> I believe this was in the full change list

In the [Change Log](https://github.com/node-red/node-red/blob/c048b1a25b36040f169f443701b9a0dde2f57914/CHANGELOG.md) from Post #1?

I did scan it twice (I'm not saying i didnt miss it)

EDIT: This comment

> [info-sidebar] Handle node/group/flows with \n in their name

kinda implies they were handling some affect in the side bar but not that nodes appearance would now render newlines.

Just thought it worth mentioning.

---

<div class="post-metadata">

**Author:** ![ristomatti](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ristomatti/32/5857_2.png) [@ristomatti](https://discourse.nodered.org/u/ristomatti)\
**Post date:** [6 June 2020 12:51 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-1-released/27761/68 "2020-06-06T12:51:32Z")

</div>

> [@Steve-Mcl](#):
>
> kinda implies they were handling some affect in the side bar but not that nodes appearance would now render newlines.

Yep, mixed it with that one. Seems like a side effect. Although it'd be odd why sidebar would handle those if the editor wouldn't.

---

<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:** [6 June 2020 13:10 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-1-released/27761/69 "2020-06-06T13:10:28Z")

</div>

> [@Steve-Mcl](#):
>
> I notice nodes now permit `\n` new lines.

It's a change that _just_ missed the 1.0 cut off and was merged in a couple days later. So it's been sat there for 6 months and to be honest, I forgot that it hadn't already shipped. The entry in the change log was getting the sidebar etc caught up.

---

<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:** [6 June 2020 14:55 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-1-released/27761/70 "2020-06-06T14:55:24Z")

</div>

> [@Steve-Mcl](#):
>
> I have found if you open the help sometimes its not populated until you click another tab
> 
> ![rede-red-v1.1.0](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/b/1/b160b6d832e174c337ae57dcc569db0a699ccb4d.gif)
> 
> #### Steps to re-produce...
> 
> - close right hand sidebar
> - refresh browser F5
> - use `CTRL+SPACE` to open sidebar
> - or action list "show help tab" or `RED.sidebar.help.show()` or `RED.sidebar.show("help")` to
> 
> - click debug tab button or context then back to **help** panel
> 
> Additionally this happens with the info panel too

Can anyone else verify this? Or is it just my problem?

---

<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:** [8 June 2020 10:23 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-1-released/27761/71 "2020-06-08T10:23:55Z")

</div>

I am seeing that with this version it takes about twice as long to load the editor in the browser. With 1.0.6 it takes about two seconds, with the beta it takes about 4.5 seconds. That is running both node-red and the browser (Waterfox) on Ubuntu 19.10 on an i5. Switching between the versions shows a consistent difference.

---

<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:** [8 June 2020 10:27 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-1-released/27761/72 "2020-06-08T10:27:23Z")

</div>

Hi @Colin - can you give a sense of how large your workspace is? Rough number of tabs, nodes etc?

The introduction of the outliner does mean there is more work to do when loading up the editor initially - and there is probably still some room for optimisation there. This is also one of the reasons we introduced the progress bar on loading - is there a particular point on the progress bar where it pauses?

---

<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:** [8 June 2020 11:12 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-1-released/27761/73 "2020-06-08T11:12:11Z")

</div>

I have 17 tabs (several of which are disabled) and about 100 nodes I should think. It seems to take about about equal times loading nodes, loading flows and adding flows.

---

<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:** [8 June 2020 11:13 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-1-released/27761/74 "2020-06-08T11:13:43Z")

</div>

> [@Colin](#):
>
> I am seeing that with this version it takes about twice as long to load the editor in the browser.

Hi @Colin, @knolleary. I am seeing the same behaviour. 14 tabs, 110 nodes. Projects is enabled.

---

<div class="post-metadata">

**Author:** ![zenofmud](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/zenofmud/32/316_2.png) [@zenofmud](https://discourse.nodered.org/u/zenofmud)\
**Post date:** [8 June 2020 11:38 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-1-released/27761/75 "2020-06-08T11:38:23Z")

</div>

platform: macOS 10.14.6 2.5 Ghz 8GB memory  
20 tabs - 850 nodes (per flow inspector - 637 are ui\_spaces nodes!)  
v1.0.6 startup 3 seconds  
v1.1.0-beta.1 startup 8 seconds

---

<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:** [8 June 2020 12:15 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-1-released/27761/76 "2020-06-08T12:15:33Z")

</div>

Is it possible that the progress bar itself could be part of the problem?

---

<div class="post-metadata">

**Author:** ![kuema](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/kuema/32/6542_2.png) [@kuema](https://discourse.nodered.org/u/kuema)\
**Post date:** [9 June 2020 09:22 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-1-released/27761/77 "2020-06-09T09:22:14Z")

</div>

For comparison, I've just tried it with one of our bigger projects at work on my local machine.

- **Flow stats:** tabs: 33, subflows: 18, nodes: 5061
- **Platform:** Win10, Core i7-7700K, 32GB memory
- **Browser:** Chrome 83.0.4103.97 (Official Build) (64-bit)
- **v1.0.6 startup:** 3-4 seconds
- **v1.1.0-beta.1 startup:** 8-10 seconds

IMO, no big deal for the _huge_ benefit of the new outliner. And the progress bar gives a nice feedback that work is being done instead of just blocking the UI.

The outliner in conjunction with groups will be a killer feature for these kind of projects we have to deal with. Especially that it reflects nested groups in the tree structure. A huge gain for a clean overview and flow structure. 🤓

Some additional ideas regarding the outliner:

- a "collapse all" button for the tree
- display the node type (especially if it should replace the "configuration node" sidebar)
- automatically reflect the node selection of the workspace in the outline and vice versa; preferably to be toggled with a button, similar to the [link with editor feature](https://codeyarns.com/2015/03/01/link-with-editor-feature-of-eclipse/) of the Eclipse IDE

All in all, a very impressive update. I am really looking forward to this next version! Thank you. 🙂

---

<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:** [9 June 2020 12:07 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-1-released/27761/78 "2020-06-09T12:07:00Z")

</div>

Minor glitch - maybe nothing to do with the beta - just random cosmic rays? 🙂

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/d/0/d0936916d6d6769c6d1fcf9ae0e58e8425195b52.jpeg)

I was not getting anything out of port 2 (or 1) when msg.payload was "phone is ringing" - tried several times

Attached the debug nodes (they weren't there in first place) and msgs started coming out of port 2

[edit] I'm now starting to wonder about the logic that I've put in place![/edit]  
[edit2]I think the logic is OK 🙂 [/edit2]

---

<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:** [11 June 2020 08:23 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-1-released/27761/79 "2020-06-11T08:23:23Z")

</div>

I'm re-reporting this glitch as I can't see it in the list of known issues - is it just me that's getting it?

> [@tada Node-RED 1.1.0-beta.1 released](https://discourse.nodered.org/t/node-red-1-1-0-beta-1-released/27761/38):
>
> Weird glitch - can repeat this Happens when exiting editing a node and then selecting another loose node (doesn't happen with nodes already connected) NR on Win10 - browser Chromium on Pi4

---

<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 2020 08:39 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-1-released/27761/80 "2020-06-11T08:39:44Z")

</div>

> [@cymplecy](#):
>
> I'm re-reporting this glitch

I haven't been able to reproduce it. It certainly is weird - something is triggering the browser's native drag/drop.

---

<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:** [11 June 2020 10:25 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-1-released/27761/81 "2020-06-11T10:25:46Z")

</div>

Tried it out using my Win10 Chrome browser instead of my Pi4

Not as repeatable as I first reported but its there

 ![simonsays1](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/3/3/33b26f9a4025ec152f63fef091bd93e935d3b85f.gif)

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

[Next page](https://discourse.nodered.org/t/node-red-1-1-0-beta-1-released/27761.md?page=5)
