NPM stopped returning the maintainers key from the registry when viewing a versioned package. Is this intentional? Nobody knows. I have a support ticket open with NPM since last Thursday, and the thread on GitHub Communities hasn't seen a response. This change has prevented the Homebridge UI from showing a plugin's author, as well as showing users that there is a Homebridge UI update from within Homebridge.
:bulb: Proposed solution
Unfortunately, users will not see that there are Homebridge UI updates until maintainers is manually added to package.json. This key is supposed to be set by NPM themselves, but it appears that you can set it yourself. I copied the maintainers from the top-level package metadata here. This change can eventually be reverted if NPM starts setting maintainers in the versioned package metadata again, or if #2079 is merged, and some amount of time has passed to ensure users have updated their Homebridge UI.
:recycle: Current situation
NPM stopped returning the
maintainerskey from the registry when viewing a versioned package. Is this intentional? Nobody knows. I have a support ticket open with NPM since last Thursday, and the thread on GitHub Communities hasn't seen a response. This change has prevented the Homebridge UI from showing a plugin's author, as well as showing users that there is a Homebridge UI update from within Homebridge.:bulb: Proposed solution
Unfortunately, users will not see that there are Homebridge UI updates until
maintainersis manually added topackage.json. This key is supposed to be set by NPM themselves, but it appears that you can set it yourself. I copied themaintainersfrom the top-level package metadata here. This change can eventually be reverted if NPM starts settingmaintainersin the versioned package metadata again, or if #2079 is merged, and some amount of time has passed to ensure users have updated their Homebridge UI.