use update-notifier

[financial-times]

use update-notifier

[AlbertoElias]

There are three different update related issues, this one, #43 and #39 With the new obt, what should we do about this? Is semver plus update-notifier a good option?

[triblondon]

I don't have much of an opinion other than that we should def notify people that there's an update available.

[AlbertoElias]

The problem that update-notifier seems to have is that the build tools would need to be listed in the npm registry

[samgiles]

Is listing in the npm registry such a bad idea? Devs can install using npm install origami-build-tools or something similar rather than using master at whatever time they install.

[triblondon]

Personally I'd rather we didn't. Isn't there something we can use that just checks git? All it needs to do is a git ls-remote.

[AlbertoElias]

Another option might be to check https://github.com/Financial-Times/origami-build-tools/releases/latest and compare that with the current git tag or maybe even with the version in the package.json file

[AlbertoElias]

Or maybe even simpler, compare the current version in the package.json file with the version in master

Suggestions? @triblondon @kavanagh @matthew-andrews @samgiles

[triblondon]

You don't want to do that every time you run a command though. How do update notifiers keep track of how often they are checking for updates?

[AlbertoElias]

Oh no, I would see if the update check had run in the last 24h, and if not, do it. That's how update-notifier does it I believe

[triblondon]

Cool, do it.

On 14 October 2014 12:27, Alberto Elias [email protected] wrote:

Oh no, I would see if the update check had run in the last 24h, and if
not, do it. That's how update-notifier does it I believe

—
Reply to this email directly or view it on GitHub
#44 (comment)
.

[AlbertoElias]

Can these be closed now that #81 is merged?