The answer seems to be that, at least in the test that Steve made available, the module node is NOT included in the export. Which is pretty much what I expected.
Do you have truly nothing else to do, other than seeing bears on the road?
All your concerns already exist at this moment, i am only asking for a color, icon and a rendered node in the palette, nothing different than copy/pasting a function node within the flow.
And no it is not the same as a sublow, as that requires its own scaffolding.
Was much of my job for many years decades. And I think my posts speak for themselves in terms of positivity and warnings as needed.
Indeed, but how many other people in this forum understand the issues I wonder?
Anyway, your very valid idea prompted me to look more deeply at part of Node-RED I'd made assumptions about. That in turn made me realise that there are some shortcomings in how the function node package manager is dealing with things.
The difference is in the length and complexity already present in the palette sidebar. And maybe the further exposure of a feature that currently has some limitations and that may well lead people with minimal knowledge of node.js package management to make unwarranted assumptions. Personally, I don't want more things cluttering up the palette sidebar, but that's just my view.
I'm also using a library stored in msg and saved to global context to get around this issue and agree that a better solution ought to be formalized in NR. Skeptical about the UX of having lib module nodes be "another type of" function node rather than their own thing.
Now if we could just keep the module source in an external file the world would be a better place.
And have an official method for adding function node external modules in settings.js maybe - other than bunging them into the global context? So saving the need for any extra nodes. Though keeping that as an option as well ideally.
I am working on a plugin (side project) that connects VSCode to Node-RED over admin APIs, pulls and shows diffs, keeps local copy where you can edit functions in the IDE (with node-red completions and full references) then push back (deploy) from VSCode to Node-RED)
This gets around the extensive changes required to the RED storage that would otherwise be required.
Will that allow a module to be used in multiple node red systems?
