# Node publishing

**URL:** <https://discourse.nodered.org/t/node-publishing/1042>\
**Category:** General\
**Created:** [25 June 2018 05:21 UTC](https://discourse.nodered.org/t/node-publishing/1042 "2018-06-25T05:21:38Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![PizlaTheDeveloper](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/pizlathedeveloper/32/793_2.png) [@PizlaTheDeveloper](https://discourse.nodered.org/u/PizlaTheDeveloper)\
**Post date:** [25 June 2018 05:21 UTC](https://discourse.nodered.org/t/node-publishing/1042/1 "2018-06-25T05:21:38Z")

</div>

Hi,  
I published my first nodes for Node-RED two days ago as node-red-contrib-foxtrotnode. But I can't find it in Node-RED's pallete manager to install. Can you give me some advice what I did wrong?

> **[PizlaTheDeveloper/Foxtrot-Node-Red](https://github.com/PizlaTheDeveloper/Foxtrot-Node-Red)**
>
> Tecomat Foxtrot node for Node-RED. Contribute to PizlaTheDeveloper/Foxtrot-Node-Red development by creating an account on GitHub.

Thank you very much

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [25 June 2018 13:51 UTC](https://discourse.nodered.org/t/node-publishing/1042/3 "2018-06-25T13:51:03Z")

</div>

Best to jump onto Slack and ask Nick to give the update process a kick.

---

<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:** [25 June 2018 14:04 UTC](https://discourse.nodered.org/t/node-publishing/1042/4 "2018-06-25T14:04:08Z")

</div>

No idea why it didn’t get picked up by the automatic process. Have poked it and its there now.

---

<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:** [25 June 2018 14:17 UTC](https://discourse.nodered.org/t/node-publishing/1042/5 "2018-06-25T14:17:29Z")

</div>

Spoke too soon... the flow library just removed it because it didn't show up on npm's search results for modules with the `node-red` keyword. Which is odd as your module definitely does have that keyword.

So something else is going on here - need to dig into it a bit more.

[Update]

@PizlaTheDeveloper if I [search npm](https://www.npmjs.com/search?q=foxtrotnode) for `foxtrotnode` it finds your module, but curiously, the search result looks like this:  
 ![foxtrotnode_-_npm_search](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/f364f25ae8eb3a05be98e2a432dce9c35d3f2b15.png)

So something is up with your node's listing on npm. Its individual registry entry looks fine to my untrained eye - [http://registry.npmjs.org/node-red-contrib-foxtrotnode](http://registry.npmjs.org/node-red-contrib-foxtrotnode)

All I can suggest is to try publishing a new version to nudge npm into reindexing your node.

---

<div class="post-metadata">

**Author:** ![PizlaTheDeveloper](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/pizlathedeveloper/32/793_2.png) [@PizlaTheDeveloper](https://discourse.nodered.org/u/PizlaTheDeveloper)\
**Post date:** [26 June 2018 06:54 UTC](https://discourse.nodered.org/t/node-publishing/1042/6 "2018-06-26T06:54:53Z")

</div>

Thank you for your advice! You’re right, search results are really weird… But I don’t know why ☹ I am new to node and npm. I can’t find any information about this issue, so I will need to contact the npm support.

---

<div class="post-metadata">

**Author:** ![S474N](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/s474n/32/5331_2.png) [@S474N](https://discourse.nodered.org/u/S474N)\
**Post date:** [22 January 2019 10:29 UTC](https://discourse.nodered.org/t/node-publishing/1042/7 "2019-01-22T10:29:13Z")

</div>

Some progress? Can you contact me please?

---

<div class="post-metadata">

**Author:** ![ukmoose](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ukmoose/32/13_2.png) [@ukmoose](https://discourse.nodered.org/u/ukmoose)\
**Post date:** [22 January 2019 10:31 UTC](https://discourse.nodered.org/t/node-publishing/1042/8 "2019-01-22T10:31:31Z")

</div>

What progress are you looking for?

The node is published and available via manage palette or [flows.nodered.org](http://flows.nodered.org)

---

<div class="post-metadata">

**Author:** ![ukmoose](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ukmoose/32/13_2.png) [@ukmoose](https://discourse.nodered.org/u/ukmoose)\
**Post date:** [23 January 2019 13:01 UTC](https://discourse.nodered.org/t/node-publishing/1042/10 "2019-01-23T13:01:49Z")

</div>

Then open an issue on the nodes github page. You can find a link from the nodes page on [flows.nodered.org](http://flows.nodered.org)

---

<div class="post-metadata">

**Author:** ![PizlaTheDeveloper](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/pizlathedeveloper/32/793_2.png) [@PizlaTheDeveloper](https://discourse.nodered.org/u/PizlaTheDeveloper)\
**Post date:** [24 January 2019 08:57 UTC](https://discourse.nodered.org/t/node-publishing/1042/11 "2019-01-24T08:57:53Z")

</div>

Hi, I have probably no helpful advice. The node was successfully indexed automatically after few days (weeks).

---

<div class="post-metadata">

**Author:** ![jcostello931](https://avatars.discourse-cdn.com/v4/letter/j/f4b2a3/32.png) [@jcostello931](https://discourse.nodered.org/u/jcostello931)\
**Post date:** [19 April 2019 19:23 UTC](https://discourse.nodered.org/t/node-publishing/1042/13 "2019-04-19T19:23:25Z")

</div>

Did you wait a couple of weeks and then republish, or did npm randomly index the module after a couple of weeks?

I'm having the same problem with my module:

> **[node-red-contrib-nba](https://www.npmjs.com/package/node-red-contrib-nba)**
>
> Access the NBA Stats API with Node-RED

I've tried updating npm and republishing but I can't get it to index correctly.

---

<div class="post-metadata">

**Author:** ![ukmoose](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ukmoose/32/13_2.png) [@ukmoose](https://discourse.nodered.org/u/ukmoose)\
**Post date:** [19 April 2019 19:25 UTC](https://discourse.nodered.org/t/node-publishing/1042/14 "2019-04-19T19:25:49Z")

</div>

did you read the other posts from today and yesterday about the same issue?  
Which includes a workaround for an apparent issue with the npm index

---

<div class="post-metadata">

**Author:** ![jcostello931](https://avatars.discourse-cdn.com/v4/letter/j/f4b2a3/32.png) [@jcostello931](https://discourse.nodered.org/u/jcostello931)\
**Post date:** [19 April 2019 19:41 UTC](https://discourse.nodered.org/t/node-publishing/1042/15 "2019-04-19T19:41:00Z")

</div>

Thanks! I checked this thread out:

[https://discourse.nodered.org/t/node-not-updated-in-palette-manager/10354/6](https://discourse.nodered.org/t/node-not-updated-in-palette-manager/10354/6)

and requested an update on the node's [flows.nodered.org](http://flows.nodered.org) page.

Is there anything we can do for new nodes that aren't yet on [flows.nodered.org](http://flows.nodered.org)?

---

<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:** [19 April 2019 19:45 UTC](https://discourse.nodered.org/t/node-publishing/1042/16 "2019-04-19T19:45:39Z")

</div>

> [@jcostello931](#):
>
> Is there anything we can do for new nodes that aren't yet on [flows.nodered.org](http://flows.nodered.org)?

No. As I said to you on slack yesterday:

> I can’t manually add it because if it doesn’t show up in the search results, the flow library assumes it has been removed from npm so removes it from the library

I also suggested you raise an issue with the npm community regarding the search results - did you do that? I can't see anything from you on there.

---

<div class="post-metadata">

**Author:** ![jcostello931](https://avatars.discourse-cdn.com/v4/letter/j/f4b2a3/32.png) [@jcostello931](https://discourse.nodered.org/u/jcostello931)\
**Post date:** [19 April 2019 19:48 UTC](https://discourse.nodered.org/t/node-publishing/1042/17 "2019-04-19T19:48:52Z")

</div>

Wasn't sure if someone found a workaround, as ukmoose mentioned in his message.

This is my post to the npm forum from yesterday as per your recommendation:

> **[Search index for NPM module not working](https://npm.community/t/search-index-for-npm-module-not-working/6942)**
>
> Hello, I first published this npm module yesterday and republished again today: It contains the keyword “node-red” which is important so that it will be picked up by the flows.nodered.org search. However, when I search the “node-red” keyword on...