# Flows.nodered.org lists node's older version instead of latest

**URL:** <https://discourse.nodered.org/t/flows-nodered-org-lists-nodes-older-version-instead-of-latest/1142>\
**Category:** General\
**Created:** [28 June 2018 10:34 UTC](https://discourse.nodered.org/t/flows-nodered-org-lists-nodes-older-version-instead-of-latest/1142 "2018-06-28T10:34:52Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![PKGeorgiev](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/pkgeorgiev/32/1325_2.png) [@PKGeorgiev](https://discourse.nodered.org/u/PKGeorgiev)\
**Post date:** [28 June 2018 10:34 UTC](https://discourse.nodered.org/t/flows-nodered-org-lists-nodes-older-version-instead-of-latest/1142/1 "2018-06-28T10:34:52Z")

</div>

Hi,

Recently node-red-contrib-norelite has been updated to version 2.6.1 (2.6.0 was published 2 days ago):

![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/fcceecb1ca6ef05bb45ac5d4f45754ae497b7861.png)

npmjs also seem to be updated:

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/e8a0985c839355e06d15c20aee463ba4fcaaeed9.png)

But [flows.nodered.org](http://flows.nodered.org) shows it as version 2.5.0:

![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/4b120ee4bcb9a13e479aa39cb45d899c300b7611.png)

What could be the problem?

---

<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:** [28 June 2018 17:18 UTC](https://discourse.nodered.org/t/flows-nodered-org-lists-nodes-older-version-instead-of-latest/1142/2 "2018-06-28T17:18:38Z")

</div>

The problem is the npm search index is out of sync.

If you search for the node, the search result shows this:

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

But when you click through to the modules own page, it shows 2.6.1.

The flow library uses the search results to find modules with the `node-red` keyword. It uses the information in those results to determine if the module needs updating or not. If the search result shows an old version, then we don't do anything.

I suggest you raise this with npm - we've seen a few individual instances of the search index being out of sync recently.

---

<div class="post-metadata">

**Author:** ![PKGeorgiev](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/pkgeorgiev/32/1325_2.png) [@PKGeorgiev](https://discourse.nodered.org/u/PKGeorgiev)\
**Post date:** [28 June 2018 22:05 UTC](https://discourse.nodered.org/t/flows-nodered-org-lists-nodes-older-version-instead-of-latest/1142/3 "2018-06-28T22:05:57Z")

</div>

Thanks @knolleary!

I’ve raised a ticket with npm’s suport.

Will it be possible for the flow library to perform an extra step to avoid npm search cache: after finding a module via npm search, query the module itself and take the version from there? I suppose it can be done via npm api? If possible it will make install / update process more robust.

---

<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:** [28 June 2018 22:28 UTC](https://discourse.nodered.org/t/flows-nodered-org-lists-nodes-older-version-instead-of-latest/1142/4 "2018-06-28T22:28:26Z")

</div>

I specifically want to avoid doing that, as it would mean checking every single module as an individual request. As it stands, that would be close to 1500 requests every time we wanted to check for updates.

---

<div class="post-metadata">

**Author:** ![PKGeorgiev](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/pkgeorgiev/32/1325_2.png) [@PKGeorgiev](https://discourse.nodered.org/u/PKGeorgiev)\
**Post date:** [28 June 2018 22:44 UTC](https://discourse.nodered.org/t/flows-nodered-org-lists-nodes-older-version-instead-of-latest/1142/5 "2018-06-28T22:44:46Z")

</div>

That makes sense 🙂

---

<div class="post-metadata">

**Author:** ![PKGeorgiev](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/pkgeorgiev/32/1325_2.png) [@PKGeorgiev](https://discourse.nodered.org/u/PKGeorgiev)\
**Post date:** [15 July 2018 23:29 UTC](https://discourse.nodered.org/t/flows-nodered-org-lists-nodes-older-version-instead-of-latest/1142/6 "2018-07-15T23:29:07Z")

</div>

I'd contacted NPM support - the issue is being investigated: [Search results not populating properly](https://status.npmjs.org/incidents/frcp18csxlks).