🎉 Node-RED 5.0.9 and 4.1.17 released

Node-RED 5.0.9 brings a long list of fixes from the community, as well as a couple new features in the Explorer sidebar.

The Explorer sidebar now shows the change/error badges for each node and flow:
You can also reorder your flows by dragging them around in the explorer.

The monaco editor has better support for HTML content that has mixed script and css blocks - applying the right linting, auto-complete and styling for the different content types.

Full changelog here: Release 5.0.9: Maintenance Release · node-red/node-red · GitHub

We have also published 4.1.17 that includes an important security fix (also in 5.0.9) for the Projects feature.

Full changelog here: Release 4.1.17: Maintenance Release · node-red/node-red · GitHub

For docker users, both releases have been freshly built on the very latest node.js builds that include the upstream fixes for the recent CA Authority key security issues.

8 Likes

My bad, I read too fast

For docker users, both releases have been freshly built on the very latest node.js builds that include the upstream fixes for the recent CA Authority key security issues.

Thanks

Hello

Thanks for the update

How is this regarding the recent raised critical security issues with Node.js ?
I believe the bare NodeRed is not directly impacted as you don't provide the Node.js so it's the installer responsibility to update the Node.js

But what about the docker images where Node.js comes bundled in ?

Thanks

After updating to 5.0.9 I've seen one minor issue with the context menu in all Monaco editors.

It seems to have a transparent background, making the entries unreadable. I guess it's related to the Monaco update shipped in this release. No issue in 5.0.8.

It's present with both of the internal themes (dark and light).

I've tried it on Linux using a current Firefox and Chromium, a clean NR instance (no custom nodes) in a private window to rule out caching issues.

Has anyone else experienced this?

Function node, Firefox, dark theme:

Template node, Chromium, light theme:

Oh dear, that's annoying.

Could you do a test? Add a template node (html mode) and enter some HTML with a script section and a style section.

Do you get intellisense inside of the style section and inside of the script section? Assuming you do, what does the background of the info boxes that pop out look like? Are they also transparent?

Can confirm same effect on Mac firefox

Seems the context menu has lost its background colour.

Never mind that part is working fine - I miss read the OP with morning eyes as an issue with the command palette (the useful one accessed via F1 all of those commands and hundreds more are accessed, not the limited right-click context menu) and was concerned it was everywhere and related to latest works providing rich editor XP in html sub sections!

People use the right-click context menu and not just hit F1? :wink:

@kuema this is confirmed - can i trouble you to raise an issue on Node-RED repo to ensure its not forgotten?

Thanks for confirming the issue, Steve!
I've raised it on Github: Monaco context menu has lost it's background color after updating to NR 5.0.9 · Issue #6037 · node-red/node-red · GitHub

Yes, I'm used to the classic right-click menu. My generation still grew up with that one. :nerd_face:

In fact, I just learned about F1 reading your post. This opens up a whole new world for me! :laughing:

1 Like

I use EVERYTHING! :smiley:

Doesn't happen on Vivaldi/Windows by the way.

1 Like

This looks to be an upstream issue in monaco. I do have a temp fix, but we might wait it out: Fix transparent Monaco context menu by disabling shadow DOM by Steve-Mcl · Pull Request #6038 · node-red/node-red · GitHub

2 Likes

Looking at the Monaco releases, this might take a while.

September was the last release, so that might not be the problem. The backlog of 790+ Issues and 90+ PRs might be more of a problem, i.e. getting the fix into the next release might become the problem.

Why not just revert to last good working version of monaco and release 5.0.10.beta1 as the new 5.0.9. At least then we can upgrade to include the other changes in 5.0.9.

Nah, not really worth it in terms of effort vs benefit when you consider what would be lost (auto completions, syntax checking, CSS support on nested blocks, Vue & vuetify language support, attribute completions and link to docs references in dashboard2) - if anything the temporary pr I raised would be my first choice, It's just I've not had time to check everything to make sure taking it out of shadow dom doesn't get interference by themes or css properties from 5000+ contrib nodes. I'm like 98% certain it'll be fine. And in the end, the context menu issue is a very minor inconvenience. So...

@kuema I didnt think to mention, all the PR does is switch on an option you could switch on yourself - so, as a temporary workaround you can add useShadowDOM: false to your settings.js

Add it as editorTheme.codeEditor.options.useShadowDOM

...
    editorTheme: {
        codeEditor: {
            lib: "monaco",
            options: {
                // dont use shadow dom for the editor
                useShadowDOM: false // <<<<< here
            }
        }
    },
...

The issue is that the context menu will be clipped by edges e.g:

Its slightly less bothersome than a transparent background and only witnessed if you right click near the right hand edge of the editor.

1 Like

Thanks, Steve!

No worries, I didn't think of that either, but that's an easy workaround for now.

Just tested it, at least the menu is usable again. :slightly_smiling_face:

1 Like

I notice I get the error notification on disabled functions. I often save functions, even if there are errors, to remember what I tried and in case I want to reuse some of the code elsewhere. I disable them so they don't affect anything else and just leave them.

With the update I now have a bunch of flows with error notifications but that simply isn't accurate since every error is on a disabled function that I'm actively saving for myself.

So is there a way for the notification to ignore disabled nodes? Thanks.

Where are you seeing these "notifications" - if you mean the triangle above the function then this has been the case for a long time - image below shows a disabled function with error in Node-RED 4.0.9

I mean in the flow tab bar:
image

ok, so 5.0.9 has not introduced this, only surfaced it (error markers on the tabs were added in 5.0.9).

This could be considered either a bug or a feature request - "dont show error triangles for disabled nodes" but it would need to be raised as an issue on the node-red repository so its not missed/lost.

2 Likes

Were the v5.0.9 Docker images updated yesterday(Oct 30th)?

a good question to @hardillb