Palette Manager and Flows Site can't cope with a package containing nodes and plugins

Core Development
1

Hi all, I think this has been raised before.

But there is still an issue with the Palette Manager and now I see a similar issue (I think?) with the Node package listings in the flows site.

The UIBUILDER package contains multiple nodes and it contains both an editor and a runtime plugin.

The palette manager shows:

image
image701×172 4.67 KB

Which is clearly incorrect.

The flows site shows nothing at all. Neither the plugins nor the nodes.

Tested with NR v4.0.9 both on Windows 11 and on Debian Linux.

2

There are a couple different things here - the palette manager and the flows site.

Has the flows site ever listed the nodes in your package? Looking at the code, the way you have structured things (by moving the registerType call out of your .html file) means the simple parsing done by the flow library won't find it. That isn't related to the fact you've also got plugins in there.

Hi all, I think this has been raised before.

Yes, you raised an issue here: Palette Manager not showing list of nodes and plugins for a package · Issue #4865 · node-red/node-red · GitHub
And you posted to the forum here: Ongoing bugs in the Manage Palette display

THe PR to fix it is here: Support for a module with nodes and plugins in the palette by GogoVega · Pull Request #4945 · node-red/node-red · GitHub

It needs reviewing, testing and merging - then it'll be available in either 4.0.10 or 4.1

Nick

3

Thanks Nick. Wasn't sure whether things had gotten lost.

Honestly, I'm not sure - I don't often look at the entry for my own package since its been there over a decade now. :grin:

That is relatively resent - I've slowly been restructuring to make the management of the code much easier.

Not sure why that needs parsing at all though since all of the required information is available in the package.json file?

4

No it isn't.

The package.json file includes a list of node files. Each node file can contain any number of actual nodes. Each node has a type, colour, icon etc - none of that information is in the package.json file.

5

Darn it, I keep forgetting that as I've never liked doing things that way.

Of course, my bad.