Sharing config nodes between separate packages

[BartButenaers]

@mdkrieg

What if I separate out this configuration node into yet a third package and make it a dependency of both of my user-level packages, this should be a viable solution right? I guess my only question is will I need to register this config-level node with nodered.org or just publish it to npmjs?

Hi Matthew,
We had a discussion last week (see here) which might give you some ideas, because it was also about code sharing.

@mdkrieg

I tried adding the following checks before registering the node in both the .js and .html files but I was still getting warnings about an already registered node

It is not clear to me why that code snippet doesn't work. At first sight it seems a reasonable good idea to me. Would be nice if somebody could enlighten the both of us...

Bart