Getting 2016 version with @latest

[jcalmeida]

Hi, For some reason, my module has regressed to the 2016 version ( 2016-02-16 09:22:01.000000000 +0000 index.js). I did "sudo npm uninstall -g --unsafe-perm homebridge-http" and then "sudo npm install -g --unsafe-perm homebridge-http@latest", to make sure I had a clean version, and it says it installs the correct version, 0.9, but the index.js file is old, from 2016.

Is this something from my side? Can't figure out what.

I'm using a Raspberry Pi.

[NovaGL]

Sorry. I think I did something I'll just to reverse the merge

[jcalmeida]

the merge was great, hope you can manage to keep it, because I was counting on that fix of the status with the json.

[NovaGL]

Oh. I don't have any devices for homebridge so what do you want. New version or old version I can't fix it as I don't know how anymore

[jcalmeida]

The new version, that you merged seems fine to me. It fixes a json error.

The issue here is that npm is fetching and older file, not the most recent. I don’t know much about this. Maybe it needs a new release?

On Wed, 9 Dec 2020 at 00:18, NovaGL notifications@github.com wrote:

Oh. I don't have any devices for homebridge so what do you want. New version or old version I can't fix it as I don't know how anymore

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/rudders/homebridge-http/issues/94#issuecomment-741297205, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABWTFXJNJMWSU5QDJ4J4R6LST266DANCNFSM4USVWRMA .

[NovaGL]

Thanks for the clarification. I'll don't know how to push new versions to npm

[jcalmeida]

Me neither. I don’t even know if what I said makes sense :) I’ll try to ask around to see if someone makes sense of this. In the meantime, I’ll fix the file on my end.

On Wed, 9 Dec 2020 at 00:25, NovaGL notifications@github.com wrote:

Thanks for the clarification. I'll don't know how to push new versions to npm

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/rudders/homebridge-http/issues/94#issuecomment-741307104, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABWTFXLJUETHLQE27G4YFFTST27WLANCNFSM4USVWRMA .

[jcalmeida]

Ok, so, if I do this : "sudo npm install -g https://github.com/rudders/homebridge-http", it installs the right version, a clean clone and it gets the fixed version of index.js

If I do this: "sudo npm install -g homebridge-http", it installs an old version with the state bug in it.

I don't know much about this, but it seems the npm repository needs to be updated. I'm fine with it for now, but more people may have this problem. Everyone who uses the homebridge GUI to install/update this will get a wrong version.

@NovaGL , maybe it was already wrong before your merge, can't tell for sure. Please keep the merge and, if possible, fix this update version, or try to find another contributor who knows how. Thanks