Upon error, check for new version and suggest to upgrade

[anibalsolon]

When an unhandled exception happen, check if the current installed version is the last one. The check should fail silently and timeout quick. Print out the upgrade command in case the version is older than what's published in npm.

[soichih]

Exceptions/errors could happen due to many different reasons (not just out-dated CLI), but the bottom line is that, user should never see "unhandled exception"; CLI should be updated with proper try/catch in various exception throwing sections of the code.

I do think it's a good idea to always check for outdated CLI installation upon execution, and display warning messages. I think CLI can download the package.json from the master branch of this repo and see if it matches the version listed in package.json

import fetch from 'node-fetch';
import fs from 'fs';

async function check() {
    const masterPackage = await fetch("https://raw.githubusercontent.com/brainlife/cli/master/package.json").then(res=>res.json());
    const thisPackage = JSON.parse(fs.readFileSync("package.json"));
    if(thisPackage.version != masterPackage.version) {
        console.log("master branch version doesn't match this the installed version");
    }
}

check();

By the way, if a user wants to ensure that they always use the latest version of CLI, they can add this to .bashrc

function bl {
    singularity run docker://brainlife/cli $@
}

singularity makes sure that it has the latest version of docker container cached locally and it will download the latest version if it's not up-to-date. See https://brainlife.io/docs/cli/install/#docker-container

[anibalsolon]

Handling the errors / catch-all would be very good, more user friendly

[soichih]

Actually I shouldn't just look at master branch's package.json. I should somehow query the current version from npmjs

npm show brainlife version

and compare it against the version in ./package.json. If we can assume that brainlife CLI is always installed via npm, and if npm command is available, we can just run the above command to show the current release version, but I am not sure if we can make that assumption or not