# 🎉 Node-RED 1.3.1 released

**URL:** <https://discourse.nodered.org/t/node-red-1-3-1-released/43867>\
**Category:** News\
**Created:** [8 April 2021 14:19 UTC](https://discourse.nodered.org/t/node-red-1-3-1-released/43867 "2021-04-08T14:19:44Z")\
**Posts on this page:** 14\
**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:** [10 April 2021 14:13 UTC](https://discourse.nodered.org/t/node-red-1-3-1-released/43867/21 "2021-04-10T14:13:44Z")

</div>

Is this the expected process, or have I missed something?

> [@Paul-Reed](#):
>
> I assume that removal of unused modules within `externalModules` is something that may be developed in the future, and until then we need to manually edit the externalModules package.json to remove the reference, delete the package, and restart node-RED.

---

<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:** [10 April 2021 15:15 UTC](https://discourse.nodered.org/t/node-red-1-3-1-released/43867/22 "2021-04-10T15:15:59Z")

</div>

Yes, removing unused modules is a manual process currently. There's no big harm leaving them there other than the disk space they take up - if the function node isn't configure to load it, it won't get loaded.

---

<div class="post-metadata">

**Author:** ![RASelkirk](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/raselkirk/32/57425_2.png) [@RASelkirk](https://discourse.nodered.org/u/RASelkirk)\
**Post date:** [10 April 2021 19:46 UTC](https://discourse.nodered.org/t/node-red-1-3-1-released/43867/23 "2021-04-10T19:46:58Z")

</div>

@dceejay, that worked! I got some warnings though:

```auto
pi@pigate:~ $ sudo systemctl stop nodered.service
pi@pigate:~ $ sudo npm i -g --unsafe-perm node-red@1.3.1
npm WARN deprecated bcrypt@3.0.6: versions < v5.0.0 do not handle NUL in passwords properly
npm WARN deprecated request@2.88.0: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated bcrypt@3.0.8: versions < v5.0.0 do not handle NUL in passwords properly
/usr/bin/node-red -> /usr/lib/node_modules/node-red/red.js
/usr/bin/node-red-pi -> /usr/lib/node_modules/node-red/bin/node-red-pi
+ node-red@1.3.1
added 1 package from 1 contributor, removed 15 packages and updated 33 packages in 41.423s
pi@pigate:~ $ sudo systemctl start nodered.service

```

Then:

```auto
pi@pigate:~ $ node-red -v
10 Apr 14:43:31 - [info]

Welcome to Node-RED
===================

10 Apr 14:43:31 - [info] Node-RED version: v1.3.1
10 Apr 14:43:31 - [info] Node.js version: v12.20.0
10 Apr 14:43:31 - [info] Linux 5.4.79-v7+ arm LE
10 Apr 14:43:32 - [info] Loading palette nodes
10 Apr 14:43:35 - [info] Dashboard version 2.25.0 started at /ui
10 Apr 14:43:35 - [info] Settings file : /home/pi/.node-red/settings.js
10 Apr 14:43:35 - [info] Context store : 'default' [module=memory]
10 Apr 14:43:35 - [info] User directory : /home/pi/.node-red
10 Apr 14:43:35 - [warn] Projects disabled : editorTheme.projects.enabled=false
10 Apr 14:43:35 - [info] Flows file : /home/pi/.node-red/flows_pigate.json
10 Apr 14:43:35 - [error] Unable to listen on http://127.0.0.1:1880/
10 Apr 14:43:35 - [error] Error: port in use

```

So, all looks good, THANKS! Any idea what the warns are about, do they need updating or removal?

Russ

---

<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:** [10 April 2021 19:51 UTC](https://discourse.nodered.org/t/node-red-1-3-1-released/43867/24 "2021-04-10T19:51:08Z")

</div>

Those warning are ok. Will be fixed when we move to Node-RED 2

---

<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:** [10 April 2021 20:11 UTC](https://discourse.nodered.org/t/node-red-1-3-1-released/43867/25 "2021-04-10T20:11:11Z")

</div>

> [@RASelkirk](#):
>
> ` Error: port in use`

That is because you have started node red while it is already running

---

<div class="post-metadata">

**Author:** ![RASelkirk](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/raselkirk/32/57425_2.png) [@RASelkirk](https://discourse.nodered.org/u/RASelkirk)\
**Post date:** [10 April 2021 21:20 UTC](https://discourse.nodered.org/t/node-red-1-3-1-released/43867/26 "2021-04-10T21:20:38Z")

</div>

I wondered about that, the error message didn't come up until asking for the version info (`node-red -v`). Could that have caused it?

Russ

---

<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:** [10 April 2021 21:35 UTC](https://discourse.nodered.org/t/node-red-1-3-1-released/43867/27 "2021-04-10T21:35:04Z")

</div>

I seem to recall that `node-red -v` starts node-RED in verbose mode for debugging (I could be wrong!)  
So if node-RED was already running, you have started a second instance running which would produce that error message.

---

<div class="post-metadata">

**Author:** ![Kazzy](https://avatars.discourse-cdn.com/v4/letter/k/34f0e0/32.png) [@Kazzy](https://discourse.nodered.org/u/Kazzy)\
**Post date:** [11 April 2021 16:53 UTC](https://discourse.nodered.org/t/node-red-1-3-1-released/43867/28 "2021-04-11T16:53:09Z")

</div>

\*\* Edit 18:04 \*\*  
reinstalled NPM via `curl -qL https://www.npmjs.com/install.sh | sh` and now on 7.9.0

So what the recommended NPM to have as that script just got me 7.9.0, and i can see there a 7.9.2.

* * *

ok silly question but what happened to the Pallet menu...

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

ah ok.. after doing the upgrade it would appear NPM has not removed itself 😕

11 Apr 17:56:07 - [info] Palette editor disabled : npm command not found

`npm -v` now gives `/usr/local/bin/npm: No such file or directory`

i've used

`npm up -g --unsafe-perm node-red`

which has always worked.. but seems to have also decide to corrupt or remove itself as well.

---

<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 April 2021 19:58 UTC](https://discourse.nodered.org/t/node-red-1-3-1-released/43867/29 "2021-04-11T19:58:00Z")

</div>



---

<div class="post-metadata">

**Author:** ![nileio](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/nileio/32/9444_2.png) [@nileio](https://discourse.nodered.org/u/nileio)\
**Post date:** [13 April 2021 01:17 UTC](https://discourse.nodered.org/t/node-red-1-3-1-released/43867/30 "2021-04-13T01:17:57Z")

</div>

I just want to say thank you for the hard work and committment to this project !! those are some really amazing features !! packaging subflows as modules is very promising and I pondered on hacking something like that myself given that my subflows are out of control.

On another note, I used the `resources` directory solution for serving custom js, and updated my custom nodes but when a user does not have the latest version of node-red , the editor does not load at all, and it gets stuck on loading nodes screen. Is it possible that we change this behaviour so that it still loads the editor though a used resource cannot be found?or is this just the as-designed behavior for any node which cannot resolve a particular resource used in its editor dialoge?

---

<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:** [13 April 2021 06:33 UTC](https://discourse.nodered.org/t/node-red-1-3-1-released/43867/31 "2021-04-13T06:33:46Z")

</div>

Errrr. Not sure how we can change the behaviour of an old version. To change it you would be upgrading it.

---

<div class="post-metadata">

**Author:** ![nileio](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/nileio/32/9444_2.png) [@nileio](https://discourse.nodered.org/u/nileio)\
**Post date:** [17 April 2021 14:52 UTC](https://discourse.nodered.org/t/node-red-1-3-1-released/43867/32 "2021-04-17T14:52:56Z")

</div>

> [@dceejay](#):
>
> Errrr. Not sure how we can change the behaviour of an old version. To change it you would be upgrading it.

totally understand .. I guess it would be an ehnacement for future releases in that case to alert the user of missing resource and load the editor, not load the node at all, or perhaps report the missing resource message in the console ,etc. at the moment the only way a user gets to know is to open the Dev Tools of the browser and get to see the 404 Resource not found error in the networks tab.

---

<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:** [16 June 2021 14:53 UTC](https://discourse.nodered.org/t/node-red-1-3-1-released/43867/33 "2021-06-16T14:53:29Z")

</div>

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

---

<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 February 2023 09:46 UTC](https://discourse.nodered.org/t/node-red-1-3-1-released/43867/34 "2023-02-03T09:46:57Z")

</div>



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