# Sharing config nodes between separate packages

**URL:** https://discourse.nodered.org/t/sharing-config-nodes-between-separate-packages/47547
**Category:** Developing Nodes
**Created:** [23 June 2021 19:11 UTC](https://discourse.nodered.org/t/sharing-config-nodes-between-separate-packages/47547 "2021-06-23T19:11:18Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![BartButenaers](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bartbutenaers/32/10476_2.png) [@BartButenaers](https://discourse.nodered.org/u/BartButenaers)
#### Post date: [23 June 2021 19:45 UTC](https://discourse.nodered.org/t/sharing-config-nodes-between-separate-packages/47547/2 "2021-06-23T19:45:13Z")

</div>

> [@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](http://nodered.org) or just publish it to npmjs?

Hi Matthew,  
We had a discussion last week (see [here](https://discourse.nodered.org/t/inheritance-of-custom-nodes/47282/6)) 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

---

_[View the full topic](https://discourse.nodered.org/t/sharing-config-nodes-between-separate-packages/47547)._