Node-red-contrib-timeout not updating in flows site

General
1

Can anyone help? I've updated node-red-contrib-timeout 3 days ago to version 1.1.3 and it appeared immediately on npm as usual. It has NOT however appeared in flows.nodered.org

Pete

2

The npm search is out of sync ( if you search for your node on the npm site it is still stating 1.1.1 is the latest version)

But when you click through to the modules page, it shows the newer version

The flow library uses the search results to find modules with the node-red keyword. If the search result shows an old version, then theres nothing for the flows site to do.

You could raise an issue with npm...

3

What you can do is:

  1. go to your node's page on flows.nodered.org
  2. login via the button in the top right corner
  3. click the 'request refresh' button in the sidebar of the page

A short while later (within 20 mins), the library will do a manual check of your node and get the update. This method bypasses the search results which, as ukmoose says, having been getting out of sync more and more recently.

This method only works for nodes the flow library already knows about.

4

Thanks Nick – I’ll do that now.

Pete

5

Sorted – 5 minutes after requesting an update, it is done. I’ll remember that for future updates.

Pete