# My first node is not integrated by Node-RED flow

**URL:** <https://discourse.nodered.org/t/my-first-node-is-not-integrated-by-node-red-flow/18852>\
**Category:** Developing Nodes\
**Created:** [6 December 2019 08:10 UTC](https://discourse.nodered.org/t/my-first-node-is-not-integrated-by-node-red-flow/18852 "2019-12-06T08:10:37Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Arnaud](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/arnaud/32/14898_2.png) [@Arnaud](https://discourse.nodered.org/u/Arnaud)\
**Post date:** [6 December 2019 08:10 UTC](https://discourse.nodered.org/t/my-first-node-is-not-integrated-by-node-red-flow/18852/1 "2019-12-06T08:10:37Z")

</div>

Hi,

I have delivered yesterday my first node yesterday (18h ago) : @adeunis/node-red-contrib-adeunis-codecs  
I'm able to install it manually in node-red (under windows 10) but it seems that something is going wrong as it is not integrated by Node-RED flow.  
I don't see any clue in the documentation :-/  
Someone could help me please ?  
Thanks,

Arnaud

---

<div class="post-metadata">

**Author:** ![hotNipi](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/hotnipi/32/383_2.png) [@hotNipi](https://discourse.nodered.org/u/hotNipi)\
**Post date:** [6 December 2019 08:37 UTC](https://discourse.nodered.org/t/my-first-node-is-not-integrated-by-node-red-flow/18852/2 "2019-12-06T08:37:26Z")

</div>

[https://nodered.org/docs/creating-nodes/packaging](https://nodered.org/docs/creating-nodes/packaging)  
Check about the `keywords` I think you are missing them all.

---

<div class="post-metadata">

**Author:** ![Arnaud](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/arnaud/32/14898_2.png) [@Arnaud](https://discourse.nodered.org/u/Arnaud)\
**Post date:** [6 December 2019 09:05 UTC](https://discourse.nodered.org/t/my-first-node-is-not-integrated-by-node-red-flow/18852/3 "2019-12-06T09:05:18Z")

</div>

You're right ! Thanks.

---

<div class="post-metadata">

**Author:** ![Arnaud](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/arnaud/32/14898_2.png) [@Arnaud](https://discourse.nodered.org/u/Arnaud)\
**Post date:** [6 December 2019 09:37 UTC](https://discourse.nodered.org/t/my-first-node-is-not-integrated-by-node-red-flow/18852/4 "2019-12-06T09:37:00Z")

</div>

My node is now integrated by Node-RED flow but when I try to install it from "manage palette", the following message is displayed:  
"Installing '@adeunis/node-red-contrib-adeunis-codecs'  
Before installing, please read the node's documentation. Some nodes have dependencies that cannot be automatically resolved and can require a restart of Node-RED."

However local tests through `npm install <localpath>` were succesfull so I don't really understand the issue.

Does dependency packages ("@adeunis/codecs": "^1.3.2" in my case) must also have specific keywords or something else ? (documentation just says : "If any of the nodes have dependencies on other npm modules, they must be included in the `dependencies` property.")

---

<div class="post-metadata">

**Author:** ![cymplecy](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cymplecy/32/2773_2.png) [@cymplecy](https://discourse.nodered.org/u/cymplecy)\
**Post date:** [6 December 2019 09:48 UTC](https://discourse.nodered.org/t/my-first-node-is-not-integrated-by-node-red-flow/18852/5 "2019-12-06T09:48:03Z")

</div>

> [@Arnaud](#):
>
> @adeunis/node-red-contrib-adeunis-codecs

I don't know anything about publishing npm packages but prefixing your package with @adeunis looks very strange and unusual.

All other Node-RED packages start with node-red

---

<div class="post-metadata">

**Author:** ![Arnaud](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/arnaud/32/14898_2.png) [@Arnaud](https://discourse.nodered.org/u/Arnaud)\
**Post date:** [6 December 2019 09:58 UTC](https://discourse.nodered.org/t/my-first-node-is-not-integrated-by-node-red-flow/18852/6 "2019-12-06T09:58:15Z")

</div>

I was not really sure about that but I found other nodes like this (for instance @prescient-devices/node-red-contrib-revpi-dio by typing @ in search bar).  
In fact I have kept @adeunis as my initial npm package was @adeunis/codecs. It was quite coherent I thought.  
Maybe it is not a good idea at all ?  
Could it explain the install issue ?

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [6 December 2019 10:05 UTC](https://discourse.nodered.org/t/my-first-node-is-not-integrated-by-node-red-flow/18852/7 "2019-12-06T10:05:10Z")

</div>

> [@cymplecy](#):
>
> I don't know anything about publishing npm packages but prefixing your package with @adeunis looks very strange and unusual.
> 
> All other Node-RED packages start with node-red

That is not true. There are lots of modules that have been published under an npm scope name (which is what the `@adeunis` bit is). See [About scopes | npm Docs](https://docs.npmjs.com/about-scopes) for more information about scopes.

> [@Arnaud](#):
>
> Maybe it is not a good idea at all ?

There is absolutely nothing wrong with publishing modules under a scope. It is entirely up to you if you want to do so. One benefit is that it helps group together the different modules you may publish.

> [@Arnaud](#):
>
> My node is now integrated by Node-RED flow but when I try to install it from "manage palette", the following message is displayed:  
> "Installing '@adeunis/node-red-contrib-adeunis-codecs'  
> Before installing, please read the node's documentation. Some nodes have dependencies that cannot be automatically resolved and can require a restart of Node-RED."

There is no error there - that is the standard message you get when you try to install any node from the palette manager. The key question is - did your node install successfully or not?

---

<div class="post-metadata">

**Author:** ![Arnaud](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/arnaud/32/14898_2.png) [@Arnaud](https://discourse.nodered.org/u/Arnaud)\
**Post date:** [6 December 2019 10:24 UTC](https://discourse.nodered.org/t/my-first-node-is-not-integrated-by-node-red-flow/18852/8 "2019-12-06T10:24:05Z")

</div>

Thanks for your reply.  
In fact it works under windows.

My initial concern was to install it on a Multitech LoRa gateway (npm 2.15.1 - node-red 0.15.3)  
As it just do nothing when I click on "install" in "manage palette".... I thought that perhaps this warning popup may disturb it.  
I will try to install it through ssh to see if it helps.  
I will also check if there are somewhere some logs