🎉 Node-RED 1.3.0-beta.1 released

[bakman2]

Thanks @knolleary and all contributors, what a massive update.

For the functionExternalModules - what is the reason for the typed input field (and not just a string) ?
How are the modules getting updated and/or can specific versions be specified ?

[knolleary]

@bakman2

For the functionExternalModules - what is the reason for the typed input field (and not just a string) ?

The TypedInput will be populated with a list of the modules already used by all Function nodes - so if you want to use the same module in multiple nodes, you don't have to type it in each time, you can just select it from the list.

You can specify a version using foo@1.2.3. However, we cannot handle the case if you have two function nodes that require different versions of the same module.

In this version, you'll need to fall back to the command-line to update modules. They get installed under ~/.node-red/externalModules/. There was original a plan to have lots of buttons in the UI to let you update/remove/install extra modules, but it needed more work to get the APIs right.

[bakman2]

you don't have to type it in each time, you can just select it from the list.

awesome, thanks.

[knolleary]

@UnborN

Firefox v.86

Thanks for reporting the issue. I have recreated and pushed a fix.

[dudleyjosh]

I checked the browser console for errors related to the issue I am having with functionExternalModules... there were no errors so this is still a mystery.

[Steve-Mcl]

Were the elements present in the dom? (See my earlier posts)

Did you check the classes against the elements? (See my earlier posts)

[UnborN]

also while you are at it .. what does this return in the browser's console ? true / false ?
RED.settings.functionExternalModules

[dudleyjosh]

It returns false... but it is definitely set to true in the settings.js file as shown in one of my earlier posts?

I manually set it from the console and that makes it work correctly... but I have no idea why it isn't loading functionExternalModules from the settings.js file correctly.

I've now installed Node-RED v1.3 beta on 4 separate computers, updated the settings.js file with functionExternalModules: true,and it works as expected on all of them except my primary work computer?

[knolleary]

@dudleyjosh

It returns false ... but it is definitely set to true in the settings.js

That tells us that whatever is happening here, is happing in the runtime side.

It is very strange because nothing in the runtime will override that value if it has been set in the settings file.

[Colin]

Edit the line in settings.js so that it becomes invalid javascript and make sure the node-red will not start - that will confirm the line is being seen. If that seems ok then delete and retype the line in case there is an unprintable character causing confusion.

[dudleyjosh]

@knolleary the good news is that we can stop chasing this as I stumbled upon the issue and it had nothing to do with Node-RED (yeah)... but now I have a bizarre mystery for myself.

After @Colin suggested editing setting.js to make it invalid, I opened it with just the simple TextEdit app and I discovered the functionExternalModules: true, line wasn't in there at all. So I closed it and opened it with the BBEdit app that I often use for basic text editing and it was there????

I simply forced another save from BBEdit and then launched Node-RED again and it worked as expected.

I have no clue what bizarre state that file was in... but it is working now.

Thanks for all of the help from everyone.

[dudleyjosh]

@Steve-Mcl the mystery has been solved... Thanks for your help.

[mbonani]

I published the second BETA version of the themes.

• dark ​- npm install @node-red-contrib-themes/dark@next
• midnight-red ​- npm install @node-red-contrib-themes/midnight-red@next
• oled ​- npm install @node-red-contrib-themes/oled@next
• solarized-dark ​- npm install @node-red-contrib-themes/solarized-dark@next
• solarized-light ​- npm install @node-red-contrib-themes/solarized-light@next

Please report any issues in the theme repository on GitHub. Links above.

[knolleary]

Bumping this thread to say, we'll be published Node-RED 1.3.0 in the next week. If you've been meaning to try out the beta, but not got there yet, you've not got long left.