# Npm publish isn't updating flows.nodered.org (solved)
**URL:** https://discourse.nodered.org/t/npm-publish-isnt-updating-flows-nodered-org-solved/1452
**Category:** Developing Nodes
**Created:** [8 July 2018 20:17 UTC](https://discourse.nodered.org/t/npm-publish-isnt-updating-flows-nodered-org-solved/1452 "2018-07-08T20:17:30Z")
**Posts on this page:** 19
**Page:** 1
### Author:  [@ncherry](https://discourse.nodered.org/u/ncherry)
#### Post date: [8 July 2018 20:17 UTC](https://discourse.nodered.org/t/npm-publish-isnt-updating-flows-nodered-org-solved/1452/1 "2018-07-08T20:17:30Z")
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](http://flows.nodered.org). I do see the update on [npmjs.org](http://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
---
### Author:  [@knolleary](https://discourse.nodered.org/u/knolleary)
#### Post date: [8 July 2018 21:28 UTC](https://discourse.nodered.org/t/npm-publish-isnt-updating-flows-nodered-org-solved/1452/2 "2018-07-08T21:28:14Z")
There's an open issue with npm on this: [New node didn't show up on this site](https://discourse.nodered.org/t/new-node-didnt-show-up-on-this-site/1385/2?u=knolleary)
---
### Author:  [@dceejay](https://discourse.nodered.org/u/dceejay)
#### Post date: [8 July 2018 21:41 UTC](https://discourse.nodered.org/t/npm-publish-isnt-updating-flows-nodered-org-solved/1452/3 "2018-07-08T21:41:05Z")
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](http://flows.nodered.org) site (with your github id) , find your node and then request update
---
### Author:  [@ncherry](https://discourse.nodered.org/u/ncherry)
#### Post date: [8 July 2018 22:21 UTC](https://discourse.nodered.org/t/npm-publish-isnt-updating-flows-nodered-org-solved/1452/4 "2018-07-08T22:21:25Z")
Huge thanks, I'll keep that in mind. I have learned something new.
Thanks 🙂
---
### Author:  [@ncherry](https://discourse.nodered.org/u/ncherry)
#### Post date: [11 July 2018 22:25 UTC](https://discourse.nodered.org/t/npm-publish-isnt-updating-flows-nodered-org-solved/1452/5 "2018-07-11T22:25:53Z")
Dceejay, as soon as I figure out how to mark this solved I will. 🙂
---
### Author:  [@Folgore](https://discourse.nodered.org/u/Folgore)
#### Post date: [15 May 2019 15:44 UTC](https://discourse.nodered.org/t/npm-publish-isnt-updating-flows-nodered-org-solved/1452/6 "2019-05-15T15:44:48Z")
Sorry, but i have the same problem...when I press request refresh is update immediately?
Thank's
---
### Author:  [@knolleary](https://discourse.nodered.org/u/knolleary)
#### Post date: [15 May 2019 16:01 UTC](https://discourse.nodered.org/t/npm-publish-isnt-updating-flows-nodered-org-solved/1452/7 "2019-05-15T16:01:47Z")
The update should happen within 20 minutes of you clicking the button. What module are you trying to update?
---
### Author:  [@Folgore](https://discourse.nodered.org/u/Folgore)
#### Post date: [15 May 2019 16:03 UTC](https://discourse.nodered.org/t/npm-publish-isnt-updating-flows-nodered-org-solved/1452/8 "2019-05-15T16:03:54Z")
this nodes [https://flows.nodered.org/node/node-red-contrib-iotgemini](https://flows.nodered.org/node/node-red-contrib-iotgemini)
But maybe there are a problem with npm
---
### Author:  [@knolleary](https://discourse.nodered.org/u/knolleary)
#### Post date: [15 May 2019 16:07 UTC](https://discourse.nodered.org/t/npm-publish-isnt-updating-flows-nodered-org-solved/1452/9 "2019-05-15T16:07:56Z")
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.
---
### Author:  [@knolleary](https://discourse.nodered.org/u/knolleary)
#### Post date: [15 May 2019 16:16 UTC](https://discourse.nodered.org/t/npm-publish-isnt-updating-flows-nodered-org-solved/1452/10 "2019-05-15T16:16:45Z")
@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?
---
### Author:  [@Folgore](https://discourse.nodered.org/u/Folgore)
#### Post date: [15 May 2019 16:25 UTC](https://discourse.nodered.org/t/npm-publish-isnt-updating-flows-nodered-org-solved/1452/11 "2019-05-15T16:25:38Z")
Ok, I tried to solve the problem for permission and the file. Sorry for my request.
Thank's
---
### Author:  [@Folgore](https://discourse.nodered.org/u/Folgore)
#### Post date: [16 May 2019 06:16 UTC](https://discourse.nodered.org/t/npm-publish-isnt-updating-flows-nodered-org-solved/1452/12 "2019-05-16T06:16:08Z")
Sorry @knolleary, yesterday evening I have tried to publish a new version. For permission, you mean a permission of the file (I try)?
Thank's
---
### Author:  [@knolleary](https://discourse.nodered.org/u/knolleary)
#### Post date: [16 May 2019 20:35 UTC](https://discourse.nodered.org/t/npm-publish-isnt-updating-flows-nodered-org-solved/1452/13 "2019-05-16T20:35:03Z")
@Folgore - just checked the flow library and once I cleared out the old version it has now successfully updated your module to the latest. So whatever change you made was the right one!
---
### Author:  [@Folgore](https://discourse.nodered.org/u/Folgore)
#### Post date: [16 May 2019 21:16 UTC](https://discourse.nodered.org/t/npm-publish-isnt-updating-flows-nodered-org-solved/1452/14 "2019-05-16T21:16:59Z")
Thank'you very match 😃
---
### Author:  [@Folgore](https://discourse.nodered.org/u/Folgore)
#### Post date: [21 August 2019 22:36 UTC](https://discourse.nodered.org/t/npm-publish-isnt-updating-flows-nodered-org-solved/1452/15 "2019-08-21T22:36:48Z")
Sorry @knolleary, I am having the same problem with file .ini . Now I resolved the in the new version. For you in node-red is OK? Because I cannot see the latest vesion on library flow.
Thank's
---
### Author:  [@knolleary](https://discourse.nodered.org/u/knolleary)
#### Post date: [21 August 2019 22:40 UTC](https://discourse.nodered.org/t/npm-publish-isnt-updating-flows-nodered-org-solved/1452/16 "2019-08-21T22:40:29Z")
Fixed and now on the flow library.
---
### Author:  [@Folgore](https://discourse.nodered.org/u/Folgore)
#### Post date: [1 May 2020 19:43 UTC](https://discourse.nodered.org/t/npm-publish-isnt-updating-flows-nodered-org-solved/1452/17 "2020-05-01T19:43:02Z")
I have another problem....but I have published...but on node-red doesn't appear a new version.
Thank's
---
### Author:  [@knolleary](https://discourse.nodered.org/u/knolleary)
#### Post date: [1 May 2020 20:11 UTC](https://discourse.nodered.org/t/npm-publish-isnt-updating-flows-nodered-org-solved/1452/18 "2020-05-01T20:11:48Z")
Have you gone to the node's page in the flow library and requested a refresh?
As described in the pinned post on the forum: [⚠️Flow Library not detecting updated modules](https://discourse.nodered.org/t/flow-library-not-detecting-updated-modules/25254)
---
### Author:  [@Folgore](https://discourse.nodered.org/u/Folgore)
#### Post date: [1 May 2020 23:17 UTC](https://discourse.nodered.org/t/npm-publish-isnt-updating-flows-nodered-org-solved/1452/19 "2020-05-01T23:17:09Z")
> [@knolleary](#):
>
> Have you gone to the node's page in the flow library and requested a refresh?
Thanks, I wasn't aware of the npm issues