I've just spent to time fixing issue with my node-red-contrib-mytimeout code. I've updated github and changed the version in package.json to "2.0.0" (and again to "2.1.0: based on old Google group threads) but I still don't see an update on flows.nodered.org. I do see the update on npmjs.org. I've simply done an npm publish after all my updates and push to github. Am I missing something or do I just need to be patient? Thanks

As it does seem to have picked up the version on npm - you can also give it a poke manually - by logging into the flows.nodered.org site (with your github id) , find your node and then request update [image]

Huge thanks, I'll keep that in mind. I have learned something new. Thanks :slight_smile:

Dceejay, as soon as I figure out how to mark this solved I will. :slight_smile:

Sorry, but i have the same problem...when I press request refresh is update immediately? Thank's

The update should happen within 20 minutes of you clicking the button. What module are you trying to update?

this nodes https://flows.nodered.org/node/node-red-contrib-iotgemini But maybe there are a problem with npm

That link 404's for me - which is odd because I can see someone clicked the refresh link for it 30 minutes ago and I don't see a log event to explain when the page now 404s. But I also npm search results are currently blank for whatever you search for... some something is wrong. Will investigate.

@Folgore there is something odd about the file permissions of the files in your published module that is breaking the flow library code that tries to process the update. It also appears to have multiple desktop.ini files that should not be in there. The issue appears to be the iotgemini directory is read-only, so my code that unpacks the module to examine it cannot do so. I will look at our code to see if we can handle that better, as clearly the normal npm command line handles it. Could you try publishing a new version with the permissions fixed?

Ok, I tried to solve the problem for permission and the file. Sorry for my request. Thank's

Node-RED

Node-RED Forum

Npm publish isn't updating flows.nodered.org (solved)

Developing Nodes

knolleary 8 July 2018 21:28 2

There's an open issue with npm on this: New node didn't show up on this site

Topic		Replies	Views
Cannot update version to node Developing Nodes	8	1680	11 May 2020
Node-red-contrib-timeout not updating in flows site General	4	553	9 May 2019
My contrib node is gone from https://flows.nodered.org/ Developing Nodes	2	410	6 August 2020
⚠️Flow Library not detecting updated modules News	5	2031	23 April 2020
Script to trigger flow library update after npm publish? General	13	704	11 April 2022

Copyright OpenJS Foundation and Node-RED contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

Npm publish isn't updating flows.nodered.org (solved)

Related topics