# Cannot register Node-RED Library

**URL:** <https://discourse.nodered.org/t/cannot-register-node-red-library/1268>\
**Category:** Share Your Nodes\
**Created:** [3 July 2018 11:12 UTC](https://discourse.nodered.org/t/cannot-register-node-red-library/1268 "2018-07-03T11:12:16Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![k-harada413](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/k-harada413/32/944_2.png) [@k-harada413](https://discourse.nodered.org/u/k-harada413)\
**Post date:** [3 July 2018 11:12 UTC](https://discourse.nodered.org/t/cannot-register-node-red-library/1268/1 "2018-07-03T11:12:16Z")

</div>

Hi  
I want to publish My Node-Red Nodes, and I registered npm library as follows:

> **[node-red-contrib-nfcpy-id](https://www.npmjs.com/package/node-red-contrib-nfcpy-id)**
>
> Read the card ID (Mifare: UID, FeliCa: IDm) with nfcpy (a Python module).
> This node can't catch touchend event.

  

> **[node-red-contrib-emax-servo](https://www.npmjs.com/package/node-red-contrib-emax-servo)**
>
> this is node-red's node. control es80a(servo motor) on raspberrypi.

But these nodes are not registered Node-RED Library.  
What Shall I do?

And my colleague has the same trouble.  
He registered as fllows:

not upgraded:

> **[node-red-contrib-process-env](https://flows.nodered.org/node/node-red-contrib-process-env)**
>
> Node-RED node for process.env

not registered:

> **[node-red-contrib-simple-sendmail](https://www.npmjs.com/package/node-red-contrib-simple-sendmail)**
>
> Package for Node-RED. Send mail using nodemailer. Input all options.Input values ​​conform to nodemailer.

  

> **[node-red-contrib-simple-aws-sdk](https://www.npmjs.com/package/node-red-contrib-simple-aws-sdk)**
>
> \## Feature

Thank you.

---

<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:** [3 July 2018 11:28 UTC](https://discourse.nodered.org/t/cannot-register-node-red-library/1268/2 "2018-07-03T11:28:12Z")

</div>

Hi,

if you search for your node on npm, the search results show:

![node-red-contrib-nfcpy_-_npm_search](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d0d84f0f29c816e0703ff1ff12a9358c56f4e027.png)

The npm search index is out of sync with the module state. We rely on the search index to discover nodes.

We've been seeing a lot of this recently; need to raise it with npm to fix their search index.

Nick

---

<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:** [3 July 2018 21:06 UTC](https://discourse.nodered.org/t/cannot-register-node-red-library/1268/3 "2018-07-03T21:06:19Z")

</div>

I have raised an issue with npm as we’ve seen this happen quite often recently - [https://github.com/npm/registry/issues/366](https://github.com/npm/registry/issues/366)

---

<div class="post-metadata">

**Author:** ![k-harada413](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/k-harada413/32/944_2.png) [@k-harada413](https://discourse.nodered.org/u/k-harada413)\
**Post date:** [4 July 2018 01:18 UTC](https://discourse.nodered.org/t/cannot-register-node-red-library/1268/4 "2018-07-04T01:18:22Z")

</div>

Hi

I see.  
Thank you for raising the issue.  
I’ll study the cause that becomes this and wait to resolve it.