# 🎉 Node-RED 3.0.0-beta.4 released

**URL:** <https://discourse.nodered.org/t/node-red-3-0-0-beta-4-released/64538>\
**Category:** News\
**Created:** [30 June 2022 09:06 UTC](https://discourse.nodered.org/t/node-red-3-0-0-beta-4-released/64538 "2022-06-30T09:06:04Z")\
**Posts on this page:** 20\
**Page:** 1

<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:** [30 June 2022 09:06 UTC](https://discourse.nodered.org/t/node-red-3-0-0-beta-4-released/64538/1 "2022-06-30T09:06:04Z")

</div>

🎉 The fourth and _next final_ **beta** release of Node-RED 3.0 is now available.

**Node-RED 3.x requires at least Node 14.x or later. We recommend the current Active LTS release, Node 16.x.**

We had hoped beta.3 was going to be the last one before we got to the final release. But there were a few issues that were reported against it that we wanted to make sure were properly resolved before doing the final release. We've also happened to have a bit of a in rush of PRs from new contributors that brought some useful new features.

So here we have the **next final** beta with 24 PRs since the last beta.

If you haven't already, please read through the [release notes for beta.1](https://discourse.nodered.org/t/node-red-3-0-0-beta-1-released/62124), [beta.2](https://discourse.nodered.org/t/node-red-3-0-0-beta-2-released/62698) and [beta.3](https://discourse.nodered.org/t/node-red-3-0-0-beta-3-released/64027).

The [Change Log](https://github.com/node-red/node-red/blob/f041159aa7820d82a44ff339b501780d8858f4d5/CHANGELOG.md) has the full list of changes.

**Note** : if any issues are reported against the beta, we'll update this post to list them here. If you hit a problem, please do check back here before adding a comment.

## Known Issues

- Importing flows via Import dialog (CTRL-I) fails with a pop up error
  - PR raised to fix this
  - will update the post with a workaround (if I can find a nice easy/friendly way)

- Editor fails to load if `settings.js` file does not contain `editorTheme.codeEditor` property. The workaround is to add this property (which does exist in the default settings file):

```auto
editorTheme: {
    ...
    codeEditor: { lib: 'monaco' }
    ...
}

```

### Stopping Flows without Stopping Node-RED

(_Some how this feature didn't get mentioned in the ChangeLog..._)

We've introduced the **optional** ability to run Node-RED without the flows themselves running. We already had Safe Mode that achieved a similar result, but with this new feature, you can stop and start the flows directly from the editor. The runtime will remember the state of the flows so when Node-RED starts up, the flows will stay in the same started/stopped state.

This feature is **not enabled by default**. To enable it, you need to add the following to your settings.js file:

```auto
runtimeState: {
   enabled: true,
   ui: true
}

```

(_the exact details of that settings object may yet be tweaked before 3.0-final_)

With that set, you get a new option in the Deploy menu:

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/a/c/ac6bee1c3d6fee0a0081227f3d4c07617537728b.png)

Clicking that option will stop the flows running, but you can continue editing them and deploy changes. Whilst stopped, the Inject/Debug node buttons will be disabled.

When the flows are stopped, the menu shows a start option instead:

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/7/2/7289f8086efe9a16e71a4d86956c99500b6e659d.png)

We're interested in feedback on the UX of this. There are some bits I think we can further refine - such as have a more obvious indicator in the workspace if the flows are stopped. There is also the existing 'Restart Flows' option - which is more technically a 'Reload Flows' as it does more than just stop/start.

### Right-Click Menu

The Right-Click menu was introduced in beta.3. A few issues were raised around its behaviour on particular OS/browsers. We believe this release has addressed those issues.

### Accessing previous welcome tours

We introduced the Welcome Tour back in 2.1.0 and it has been updated for each major release. With this release, we've added a way to access the tours of the previous releases in the Help sidebar:

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/2/e/2ee347e5ce6796a1de3033565bb7d54a5d81dc41.png)

## Node Fixes

- CSV: Fix CSV node to handle when outputting text fields (#3716)
- Delay: Fix delay rate limit last timing when empty (#3709)
- Link: Ensure link-call cache is updated when link-in is modified (#3695)
- Join: Join node in reduce mode doesn't keep existing msg properties (#3670)
- Template: Add support for evalulating {{env.}} within a template node (#3690)

## Installing the beta

If you want to try out the beta, you will need specify node-red@next when you use npm to update. Without the `@next` you'll still get 2.2.x

So on a Pi you'd do:

```auto
sudo npm install -g --unsafe-perm node-red@next

```

## Reporting problems

If you hit any problems, please report them either as a reply on this topic, or in the #core-dev slack channel. Please do not post new topics to the forum regarding the beta as that could confuse users who are not using the beta.

## Outstanding work

As we've said with the last ~~two~~ three betas, this contains just about everything for the final release - but this time we mean it even even more.

There are a couple more minor PRs that I hope we can resolve for 3.0 which shouldn't require a whole new beta release. In terms of timing of the 3.0 release, the main challenge is scheduling the time it takes to do the final release. So rather than promise anything here, just know we want to get there as soon as time allows.

---

<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:** [30 June 2022 09:43 UTC](https://discourse.nodered.org/t/node-red-3-0-0-beta-4-released/64538/2 "2022-06-30T09:43:55Z")

</div>

Right-click mouse seems to be working fine on Vivaldi(chrome based) and Chrome itself on Windows 11 for me 🙂

---

<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:** [30 June 2022 12:29 UTC](https://discourse.nodered.org/t/node-red-3-0-0-beta-4-released/64538/3 "2022-06-30T12:29:48Z")

</div>

A comment in the latest settings.js file (line 286):

```auto
logging: {
    /** Only console logging is currently supported */
   console: {

```

Would seem to imply that custom logging isn't available? However, it is working as my `mqttLog` custom logger is working fine.

---

<div class="post-metadata">

**Author:** ![hardillb](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/hardillb/32/12373_2.png) [@hardillb](https://discourse.nodered.org/u/hardillb)\
**Post date:** [30 June 2022 12:49 UTC](https://discourse.nodered.org/t/node-red-3-0-0-beta-4-released/64538/4 "2022-06-30T12:49:24Z")

</div>

Docker builds done, in usual place `nodered/node-red-dev:3.0.0-beta.4`

---

<div class="post-metadata">

**Author:** ![DmitrySidorow](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dmitrysidorow/32/62008_2.png) [@DmitrySidorow](https://discourse.nodered.org/u/DmitrySidorow)\
**Post date:** [30 June 2022 13:05 UTC](https://discourse.nodered.org/t/node-red-3-0-0-beta-4-released/64538/5 "2022-06-30T13:05:12Z")

</div>

how can i catch start/stop actions in flow?

---

<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:** [30 June 2022 13:08 UTC](https://discourse.nodered.org/t/node-red-3-0-0-beta-4-released/64538/6 "2022-06-30T13:08:29Z")

</div>

For `start` - use an inject set to trigger once  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/2/d/2d9e4d26fcd2c8ced9da6fa0feca082e89734a6c.png)

For `stop` - it doesnt really make sense since the flows are stopped. However, you could always use the "on close" of a function node to perform some task.

---

<div class="post-metadata">

**Author:** ![DmitrySidorow](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dmitrysidorow/32/62008_2.png) [@DmitrySidorow](https://discourse.nodered.org/u/DmitrySidorow)\
**Post date:** [30 June 2022 13:49 UTC](https://discourse.nodered.org/t/node-red-3-0-0-beta-4-released/64538/7 "2022-06-30T13:49:52Z")

</div>

cannot import nodes, who can confirm that?

---

<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:** [30 June 2022 13:58 UTC](https://discourse.nodered.org/t/node-red-3-0-0-beta-4-released/64538/8 "2022-06-30T13:58:51Z")

</div>

> [@DmitrySidorow](#):
>
> cannot import nodes

What do you mean by that - can you provide a step by step?

---

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [30 June 2022 14:01 UTC](https://discourse.nodered.org/t/node-red-3-0-0-beta-4-released/64538/9 "2022-06-30T14:01:02Z")

</div>

A little off topic here... Sorry

But what will happen with the score card in reference to the min node version when v3 hits.  
currently, we get marked for requiring a more updated node version that is required by Node RED 2.x.x.

How is the score card going to work with 2 different min node versions (Node RED 2 vs Node RED 3)  
Will the score card remain aligned with v2 requirements?

---

<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:** [30 June 2022 14:07 UTC](https://discourse.nodered.org/t/node-red-3-0-0-beta-4-released/64538/10 "2022-06-30T14:07:42Z")

</div>

> [@Steve-Mcl](#):
>
> > [@DmitrySidorow](#):
> >
> > cannot import nodes
> 
> What do you mean by that - can you provide a step by step?

Never mind - I found it.

Issue raised - bah! silly miss by me ☹

Fixed in github. [Ensure importMap is not null when using import UI by Steve-Mcl · Pull Request #3723 · node-red/node-red · GitHub](https://github.com/node-red/node-red/pull/3723)

I will update the 1st post to include info about this (and how to work around it ASAP)

---

<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:** [30 June 2022 14:49 UTC](https://discourse.nodered.org/t/node-red-3-0-0-beta-4-released/64538/11 "2022-06-30T14:49:29Z")

</div>

Loving the right click context menu - but i have noticed a slight inconsistency in right click context menu to the available actions.

### Issue

Selecting a bunch of nodes with wires does enable context menus "insert --\> junction" or "insert --\> links" BUT you can perform these actions with the action list

![chrome_BKo1qywUi2](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/1/d/1de87db34b94cdc3b8a2a2f62e9fb272065fe853.gif)

### Proposal

Enable the "Insert --\> junction" and "Insert --\> links" when nodes with wire(s) are selected.

---

<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:** [30 June 2022 15:24 UTC](https://discourse.nodered.org/t/node-red-3-0-0-beta-4-released/64538/12 "2022-06-30T15:24:55Z")

</div>

> [@hardillb](#):
>
> nodered/node-red-dev:3.0.0-beta.4

docker pull nodered/node-red-dev:3.0.0-beta.4  
Error response from daemon: manifest for nodered/node-red-dev:3.0.0-beta.4 not found: manifest unknown: manifest unknown

Is there a typo in your post or have I done/missed something stupid...again? (Preemptive excuse: no coffee yet)

---

<div class="post-metadata">

**Author:** ![hardillb](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/hardillb/32/12373_2.png) [@hardillb](https://discourse.nodered.org/u/hardillb)\
**Post date:** [30 June 2022 15:45 UTC](https://discourse.nodered.org/t/node-red-3-0-0-beta-4-released/64538/13 "2022-06-30T15:45:27Z")

</div>

Check Docker hub first - [Docker Hub](https://hub.docker.com/repository/docker/nodered/node-red-dev)

Yes, there is a missing `v` from the tag `nodered/node-red-dev:v3.0.0-beta.4`

But it looks like a bug in the GH action as only one of the many builds has a `v` prefix

---

<div class="post-metadata">

**Author:** ![hardillb](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/hardillb/32/12373_2.png) [@hardillb](https://discourse.nodered.org/u/hardillb)\
**Post date:** [30 June 2022 15:58 UTC](https://discourse.nodered.org/t/node-red-3-0-0-beta-4-released/64538/14 "2022-06-30T15:58:56Z")

</div>

The problem is the tag name, it shouldn't have the leading `v` when created (only the beta's have this problem, will fix for final release) and it's normally not a problem as this build would have been tagged as `latest` for a release build

---

<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:** [30 June 2022 16:10 UTC](https://discourse.nodered.org/t/node-red-3-0-0-beta-4-released/64538/15 "2022-06-30T16:10:02Z")

</div>

I just wanted to report this - it seems it may have been a cache issue.

Just upgraded to 3.0.0-beta.4 and have the NASA-WildFire flow on one of my tabs of a project. Works fine but I decided to move it to a new project. I selected the tab and exported it to the clipboard and created a new project. When I tried to import it This popped up:  
 ![Screen Shot 2022-06-30 at 11.53.13 AM](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/8/5/855bba62457a25d43e223fb21abe9cc74de49b4f.png)

I went back to beta 3 and imported it fine so I tried again in beta 4 and this time cleared the caches and it imported fine.

---

<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:** [30 June 2022 17:02 UTC](https://discourse.nodered.org/t/node-red-3-0-0-beta-4-released/64538/16 "2022-06-30T17:02:26Z")

</div>

Odd - the problem was due to `importMap` not being "something" and should be 100% repeatable problem. No matter - it is fixed in GitHib (expect a beta.5 :sigh:)

for anyone else reading - this is a known issue (documented in first post)

---

<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:** [30 June 2022 18:42 UTC](https://discourse.nodered.org/t/node-red-3-0-0-beta-4-released/64538/17 "2022-06-30T18:42:45Z")

</div>

> [@knolleary](#):
>
> So here we have the **next final** beta

Nick jinxed it!

---

<div class="post-metadata">

**Author:** ![UnborN](https://avatars.discourse-cdn.com/v4/letter/u/4491bb/32.png) [@UnborN](https://discourse.nodered.org/u/UnborN)\
**Post date:** [30 June 2022 20:14 UTC](https://discourse.nodered.org/t/node-red-3-0-0-beta-4-released/64538/18 "2022-06-30T20:14:45Z")

</div>

Excellent work !

There was the PR for fixing the Ctrl+click quick-add of a node  
[Include scroll offset when positioning quick-add dialog #3685](https://github.com/node-red/node-red/pull/3685)

but it seems there is also an issue with the offset when **Right clicking --\> Insert --\> Node**  
when the flow is scrolled a bit down  
(the dialog doesnt show at the place of right-clicking)

Node-RED version: v3.0.0-beta.4  
Node.js version: v16.14.0  
OS Windows 11  
Browser: Firefox / Chrome

---

<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:** [30 June 2022 21:09 UTC](https://discourse.nodered.org/t/node-red-3-0-0-beta-4-released/64538/19 "2022-06-30T21:09:06Z")

</div>

Hey @UnborN any chance you could capture a screenshot & raise an issue?

---

<div class="post-metadata">

**Author:** ![UnborN](https://avatars.discourse-cdn.com/v4/letter/u/4491bb/32.png) [@UnborN](https://discourse.nodered.org/u/UnborN)\
**Post date:** [30 June 2022 21:22 UTC](https://discourse.nodered.org/t/node-red-3-0-0-beta-4-released/64538/20 "2022-06-30T21:22:54Z")

</div>

👍

[Issue with dialog offset when Right clicking --\> Insert --\> Node (v3.0.0-beta.4) #3725](https://github.com/node-red/node-red/issues/3725)

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