How to edit the settings.js for a nodered instance

[Peter_Madsen]

Hey all,

Has anyone figured out how to edit the settings.js file for a Node-RED instance to include custom built-in functionalities — specifically to make globally accessible classes available in the function nodes?

I’m trying to find a clean way to add a custom class (with methods and styling logic) to the global context so I can use it across function nodes, with proper linting and IntelliSense.

For example:

ansify("Rainbow").bold.fg_rainbow

This works perfectly within the same function node where I define the StyledString class and the ansify() function. But once I try to use it elsewhere via global.get("ansify"), the runtime works — but I lose autocompletion and linting.

Here’s what I’d love to achieve:

• Load my custom class globally using functionGlobalContext in settings.js
• Get full IntelliSense (as if it were a built-in class)
• Keep the chainable style (.bold.fg_red.glitch, etc.) with autocomplete support across nodes

Eg.

this only work inside the same function node where i have defined the class

[Anono_Nono]

looking for a way to do that as well. i want to add the theme: "dark-scroll" setting to the editorTheme, but it’s not picking it up. watching…

[Allan_Zimmermann]

You clone this repo

GitHub - openiap/noderedagent

Then make the changes in src/index.ts after line 89
Test it, and when it work run ‘npm run build’ and the use pack and publish to push it to your opencore. Afyer this you can the run this package in any agent both locally and remote.