A way to cause a resync of modules that have changed while local-npm has been offline

[ivanwills]

It would be good if there was a way to get local-npm to re-sync with the up-stream registry if local-npm wasn't running when that module changed (ie didn't get the event for the change)

[nolanlawson]

If it gets out-of-sync, then that's a straight-up bug. PouchDB should handle this correctly. Can you do a npm ls -g and see which version of PouchDB you have installed along with local-npm?

[tomchentw]

I'm experiencing the same issue with local-npm@1.6.0 and pouchdb@5.4.5. I love local-npm and it really speeds up my development time, but this sync issue is quite annoying.

---

Update: node v6.6.0 npm 3.10.7

[fivetanley]

I have hit this also. @nolanlawson I know the project is unmaintained but if you have any place I could look in the local PouchDB servers for debugging info I'd appreciate it.

[nolanlawson]

If anyone can track this down and repro it consistently, that would be awesome. I fear it's an issue in PouchDB sync itself that only crops up in heavy use situations such as local-npm. Either that or it's an issue with npm's skimdb server, which is using an old fork of CouchDB afaik.

[gabrielcsapo]

@fivetanley have you been able to reproduce this with local-npm@^2?

[givo]

We have the same problem.

We are restricted to use a private network in our company so we use local-npm as an offline npm registry like so:

• installed v2.2.1 on a machine connected to the internet (windows)
• run local-npm --url http://${machine_ip}:5080
• installed desired packages on a different machine on the same home network
• imported local-npm directory to a server on the business' offline network
• everything work like a charm

But when we need a new package or to update an existing one, we went to the online machine, run local-npm and the server doesn't update his old packages, even if try to npm install package@{desired_version}

please help.