Node-RED 4.1 have been published and is now generally available!
The release blog post is here: Version 4.1 released : Node-RED
Thank you to everyone who contributed to this release.
13 Likes
Docker builds should be available both on Docker Hub and GitHub
1 Like
Tbh, it annoys me more than I thought it would 
5 Likes
All the more important to set up sensible keyboard shortcuts.
I have Esc set up to exit, ctrl-Enter is Done.
4.1 release (like previous release) loads my flows by default with the deploy button enabled (dirty flows?).
Nothing weird to be seen in console.
[Log] [Wipr (Legacy) Extra 1.71] Not required on this domain (wipr-extra.js, line 2)
[Log] JQMIGRATE: Migrate is installed, version 3.5.2 (vendor.js, line 3)
[Error] Source Map loading errors (x4)
[Error] Failed to load resource: the server responded with a status of 404 (Not Found) (jquery-steps.css.map, line 0)
[Error] Failed to load resource: the server responded with a status of 404 (Not Found) (purify.min.js.map, line 0)
[Error] Failed to load resource: the server responded with a status of 404 (Not Found) (FileSaver.min.js.map, line 0)
[Error] Failed to load resource: the server responded with a status of 404 (Not Found) (jquery-steps.css.map, line 0)
[Log] Node-RED: 4.1.0 (red.min.js, line 16)
[Log] Versions (red.min.js, line 16)
[Log] jQuery – "3.7.1" (red.min.js, line 16)
[Log] jQuery UI – "1.14.1" (red.min.js, line 16)
[Log] ACE – "1.4.12" (red.min.js, line 16)
[Log] MONACO – "0.52.0" (red.min.js, line 16)
[Log] D3 – "3.0.3" (red.min.js, line 16)
[Log] Projects disabled (red.min.js, line 16)
[Log] registering netatmo get next events (10.0.0.170, line 2)
[Log] registering netatmo get camera picture (10.0.0.170, line 2)
[Log] registering netatmo get home data (10.0.0.170, line 2)
[Log] ui_worldmap: Node-RED-Dashboard not found. (10.0.0.170, line 268)
[Warning] registerType: e-mail mta: the property "users" is internal and cannot be used. (red.min.js, line 16)
[Log] =======================> HIER configNodes via eachConfig nodig (10.0.0.170, line 231)
[Error] TypeError: undefined is not an object (evaluating '(0,Z.fz)().navigator.clipboard.write')
e (editor.js:2:4202081)
Navigating away also shows native browser message that there is unsaved data.
Safari 18.5 (20621.2.5.11.8)
MacOS 15.5 (24F74)
node -v && npm -v
v20.19.2
10.8.2
What module have you installed for the e-mail mta node that is logging a warning?
But also, if you say you were seeing this in previous releases as well, then this isn’t a 4.1 specific item, so may be worth splitting off to its own topic?
node-red-node-email
But also, if you say you were seeing this in previous releases as well, then this isn’t a 4.1 specific item, so may be worth splitting off to its own topic?
True, i was 'hoping' this was solved as a side effect of other fixes.
When editing a subflow and clicking on the output of a node, dragging a line to an empty place on the canvas, a choice of nodes should appear. I only get an empty looking gray node with a dashed outline. I cannot make it go away unless I reload the entire page. I cannot select a node type as there are none displayed where there should be a dropdown. I’m running Node.js 22 on a raspberry pi and Node Red 4.1 upgraded from (I think) 4.0.9.
I was never a fan of this change at all!
Slows down the speed that I have learned to gain in the workspace, and now it just gets in the way 
I wish my suggestion of having it a config would have been implemented - but hey it's all good. (Really) 
2 Likes
@Mecworks can you raise an issue on GitHub?
I'm highly tempted to put it behind a user option and defaulting to the original behaviour
6 Likes
Would be nice!
The default now, has changed the way I need to work, whilst a 
- but still an interruption when working in the editor for long periods.
I'm all good with the changes of course 
, but would be nice for some flexibility here, its little detail of course, but its magnified when muscle memory is a factor within the editor.
But dare I forget - thanks for the awesome work 
I was going to add the setting but I was not sure if I could.
Once this new setting is added, we must track how many people enabled it and kept it for a while. FF could run these tests using new onboarded users who are not biased like you old folks (experienced users). @dimitrieh this could probably be one of your focuses.
2 Likes
You should share the pool link that was run with @dimitrieh
Hey less of the old, I think you mean seasoned 
1 Like
I didnt mean to be mean. I wanted to say “experienced user”
1 Like
I’ll take that with a pinch of salt..
7 Likes
