Hyper: Plugin updates are not recognized (hyperterm says "No changes!")

[trevordmiller]

I've created a HyperTerm plugin (color scheme) called nova-hyperterm.
After publishing on npm and placing the plugin in my .hyperterm.js plugins array, everything worked as expected.
I've fixed some issues and published patch versions to npm as you can see in the attached screenshot.
When I restart HyperTerm and/or go to Plugins > Update All Now, HyperTerm doesn't recognize that my plugin has been updated - it says "Plugins Updated" "No changes!".

The only way I was able to update my plugin was by deleting and re-installing the npm modules in ~/.hyperterm_modules.

p.s. Thank you for your amazing work on HyperTerm! I already love it and after these few bugs have been ironed out I think it will be the best option for a modern terminal 💪 💥 Here is what my full setup looks like with HyperTerm + Vim + Tmux (all using my custom "Nova" color scheme):

[trevordmiller]

I also tried pushing a minor version (1.1.0) and that didn't work either. It seems that the latest tag in the ~/.hyperterm_plugins/package.json isn't working correctly. If someone could take a look at this and fix it I would greatly appreciate it :) My hunch is that nobody is actually getting any updates right now. Unless there is something wrong with my package specifically, this would appear to be a global problem for all users not getting updates without a manual wipe/re-install of ./hyperterm_modules/node_modules

[trevordmiller]

It looks like there is no such thing as latest for a semver value? This might need to be switched to * for all versions? https://docs.npmjs.com/misc/semver

[ekmartin]

It seems like this is caused by the fact that we're doing npm install instead of npm update, here. It seems pretty weird though, since npm install normally updates packages if an installed package no longer is covered by the range you've defined - and for latest it seems pretty logic that this would happen when a new version is released.

Might be good to change it to update nonetheless though (if it doesn't have any negative side effects), to ensure that users always have the last version covered by their semver range. npm install won't update if the existing version already is in range, which might be both good and bad depending on who you ask.

[trevordmiller]

I'm unfamiliar with using latest in the package.json; if I were to run npm install {some-package}@latest it would always download the latest version (including patches); latest in the package.json is not behaving that way. update only updates to the matching semver range - so I would imagine it would continue to behave as it does now if the latest value isn't working; * (x.x.x would also work) is listed in the docs as the semver range to always use the latest package. I'm new to HyperTerm and am not sure what the expectations are around updates. IMO, it would be nice to auto-update to every version (including patches). Or, if auto-update isn't a good idea, then ensure the Update All Now menu option works correctly. Until this is resolved, I'll continue to manually wipe and re-npm install inside ~/hyperterm_plugins but this seems like it should be resolved soon as I don't think any HyperTerm user is getting incremental package updates after the initial install.
https://docs.npmjs.com/misc/semver

[trevordmiller]

Any updates on this? Seems to be a critical thing to fix IMO since every HyperTerm user is not getting package updates right now?

[trevordmiller]

cc: @rauchg

[trevordmiller]

According to the blog post for the version 8 release, this may be fixed? cc: @rauchg

[trevordmiller]

Still a problem. From my testing, all Hyper users are not getting package updates without a manual cd ~/.hyper_plugins && rm -rf node_modules && npm install; does the Hyper team know about this? Seems to be a critical issue...

cc: @rauchg @leo

[trevordmiller]

Closing this since there has been no activity or response.