Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Getting 2016 version with @latest #94

Open
jcalmeida opened this issue Dec 8, 2020 · 7 comments
Open

Getting 2016 version with @latest #94

jcalmeida opened this issue Dec 8, 2020 · 7 comments

Comments

@jcalmeida
Copy link

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
Copy link
Collaborator

NovaGL commented Dec 9, 2020

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

@jcalmeida
Copy link
Author

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
Copy link
Collaborator

NovaGL commented Dec 9, 2020

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
Copy link
Author

jcalmeida commented Dec 9, 2020 via email

@NovaGL
Copy link
Collaborator

NovaGL commented Dec 9, 2020

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

@jcalmeida
Copy link
Author

jcalmeida commented Dec 9, 2020 via email

@jcalmeida
Copy link
Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants