Skip to content

Getting 2016 version with @latest #94

Description

@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.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions