# Going beyond Node-RED 1.x

**URL:** <https://discourse.nodered.org/t/going-beyond-node-red-1-x/29320>\
**Category:** News\
**Created:** [1 July 2020 15:38 UTC](https://discourse.nodered.org/t/going-beyond-node-red-1-x/29320 "2020-07-01T15:38:36Z")\
**Posts on this page:** 14\
**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:** [1 July 2020 15:38 UTC](https://discourse.nodered.org/t/going-beyond-node-red-1-x/29320/1 "2020-07-01T15:38:36Z")

</div>

We've just published a new post to the Node-RED blog, that will be of interest to you all.

It describes how we plan to approach future releases of Node-RED, how that relates to Node.js releases, and when you can expect a Node-RED 2.x release.

> **[Going beyond Node-RED 1.x](https://nodered.org/blog/2020/07/01/release-plans)**
>
> With the 1.1.0 release done, it's time to think about what comes next for the project. Find out how we're proposing to approach future releases of Node-RED and what that means for longer term support.

---

<div class="post-metadata">

**Author:** ![Botched1](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/botched1/32/21190_2.png) [@Botched1](https://discourse.nodered.org/u/Botched1)\
**Post date:** [1 July 2020 16:40 UTC](https://discourse.nodered.org/t/going-beyond-node-red-1-x/29320/2 "2020-07-01T16:40:19Z")

</div>

This may be a question that is covered elsewhere, but... What is the philosophy/strategy around which node.js version is used in the container versions of Node-RED?

I believe it is currently using node.js 10.21.0, but I assume it will need to move to 12.x sometime before 4/2021?

---

<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:** [1 July 2020 17:07 UTC](https://discourse.nodered.org/t/going-beyond-node-red-1-x/29320/3 "2020-07-01T17:07:04Z")

</div>

> [@Botched1](#):
>
> I believe it is currently using node.js 10.21.0, but I assume it will need to move to 12.x sometime before 4/2021?

Good question - something we need to formalise.

We currently build both 10 _and_ 12 based images, but the default you get if you don't specify a tag is the 10-based image.

We won't change that default for the same reasons we wouldn't drop node 8/10 support without a major version change - it's a major dependency change.

---

<div class="post-metadata">

**Author:** ![Botched1](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/botched1/32/21190_2.png) [@Botched1](https://discourse.nodered.org/u/Botched1)\
**Post date:** [1 July 2020 17:25 UTC](https://discourse.nodered.org/t/going-beyond-node-red-1-x/29320/4 "2020-07-01T17:25:15Z")

</div>

Thanks, and that makes perfect sense.

You know... I'm so quick to just go to "latest" that I didn't even notice there is a "latest-12". Thanks for pointing that out to me! Should have RTFMed as it is all well documented here:

> <https://github.com/node-red/node-red-docker/blob/master/README.md>

---

<div class="post-metadata">

**Author:** ![Botched1](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/botched1/32/21190_2.png) [@Botched1](https://discourse.nodered.org/u/Botched1)\
**Post date:** [3 July 2020 16:45 UTC](https://discourse.nodered.org/t/going-beyond-node-red-1-x/29320/5 "2020-07-03T16:45:25Z")

</div>

At what point will there be Node 14 based images? After it goes "active" this fall?

Also, will there be any 1.x Node 14 based containers, or just starting with the 2.0 chain?

---

<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:** [3 July 2020 17:20 UTC](https://discourse.nodered.org/t/going-beyond-node-red-1-x/29320/6 "2020-07-03T17:20:38Z")

</div>

At the point someone generates them ? Once we have mopped up after the core 1.1, and it’s knock on effects maybe, or someone else volunteers. And yes most likely when active, though we do have a node-red-dev on dockerhub for trying things

---

<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:** [3 July 2020 17:26 UTC](https://discourse.nodered.org/t/going-beyond-node-red-1-x/29320/7 "2020-07-03T17:26:27Z")

</div>

There's no reason not to add 14 today. Just needs someone to do the work rather than the other things on the to-do list.

If anyone wants to raise a PR on the repo to add 14 builds, that would be welcome. Just remember to update the readme as well.

---

<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:** [3 July 2020 18:29 UTC](https://discourse.nodered.org/t/going-beyond-node-red-1-x/29320/8 "2020-07-03T18:29:51Z")

</div>

(Against the node-red-docker dev branch first so people can test first etc)

---

<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:** [3 July 2020 18:30 UTC](https://discourse.nodered.org/t/going-beyond-node-red-1-x/29320/9 "2020-07-03T18:30:41Z")

</div>

No `dev` branch in the node-red-docker repo.... can go straight to master.

---

<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:** [3 July 2020 18:37 UTC](https://discourse.nodered.org/t/going-beyond-node-red-1-x/29320/10 "2020-07-03T18:37:33Z")

</div>

eh ? yes there is.... that's what it's there for isn't it ?

---

<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:** [3 July 2020 18:50 UTC](https://discourse.nodered.org/t/going-beyond-node-red-1-x/29320/11 "2020-07-03T18:50:04Z")

</div>

Oops - you are right. Didn't have it checked out on this machine.

---

<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:** [7 July 2020 08:38 UTC](https://discourse.nodered.org/t/going-beyond-node-red-1-x/29320/12 "2020-07-07T08:38:22Z")

</div>

24 posts were split to a new topic: [Improved hardware support](https://discourse.nodered.org/t/improved-hardware-support/29643)

---

<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:** [7 July 2020 09:32 UTC](https://discourse.nodered.org/t/going-beyond-node-red-1-x/29320/13 "2020-07-07T09:32:39Z")

</div>

A post was merged into an existing topic: [Improved hardware support](https://discourse.nodered.org/t/improved-hardware-support/29643/28)

---

<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:** [5 September 2020 09:36 UTC](https://discourse.nodered.org/t/going-beyond-node-red-1-x/29320/14 "2020-09-05T09:36:59Z")

</div>

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