cli-setu 0.1.0

package/src/update.js

@@ -0,0 +1,73 @@
+// `setu --update` - checks the real npm registry for a newer published
+// version, and if one exists, runs the real upgrade command on the
+// user's behalf (confirmed directly: don't just tell them what to run,
+// actually run it) so they don't have to remember/type
+// `npm install -g cli-setu` themselves.
+const { execFile } = require('child_process');
+const { promisify } = require('util');
+const execFileAsync = promisify(execFile);
+const pkg = require('../package.json');
+
+// A plain https GET against the real npm registry's own JSON API - no
+// extra dependency needed just to read one field (dist-tags.latest),
+// and this works the same whether or not the user has ever run `npm
+// login` (checking the latest published version is a public, anonymous
+// read, unlike actually publishing).
+async function fetchLatestVersion() {
+  const res = await fetch(`https://registry.npmjs.org/${pkg.name}/latest`);
+  if (!res.ok) throw new Error(`npm registry returned ${res.status}`);
+  const data = await res.json();
+  return data.version;
+}
+
+// Plain, dependency-free semver comparison - good enough for this one
+// use (comparing two real, well-formed "x.y.z" versions from package.json
+// and the npm registry), not a general-purpose semver range parser.
+function isNewer(latest, current) {
+  const a = latest.split('.').map(Number);
+  const b = current.split('.').map(Number);
+  for (let i = 0; i < Math.max(a.length, b.length); i++) {
+    const x = a[i] || 0;
+    const y = b[i] || 0;
+    if (x !== y) return x > y;
+  }
+  return false;
+}
+
+async function update() {
+  console.log(`[setu] Current version: ${pkg.version}`);
+  console.log('[setu] Checking for updates...');
+
+  let latest;
+  try {
+    latest = await fetchLatestVersion();
+  } catch (err) {
+    console.error(`[setu] Could not check for updates: ${err.message}`);
+    process.exit(1);
+  }
+
+  if (!isNewer(latest, pkg.version)) {
+    console.log(`[setu] Already on the latest version (${pkg.version}).`);
+    return;
+  }
+
+  console.log(`[setu] A newer version is available: ${latest} (you have ${pkg.version}).`);
+  console.log(`[setu] Installing ${pkg.name}@${latest}...`);
+  try {
+    // execFile (not exec) - no shell involved, consistent with this
+    // project's own established convention for anything that runs a
+    // real external command (see supervisor.js's own comment on exec vs
+    // execFile for the same reasoning).
+    const { stdout } = await execFileAsync('npm', ['install', '-g', `${pkg.name}@${latest}`], {
+      shell: process.platform === 'win32', // npm.cmd on Windows needs a shell to resolve; execFile alone can't find it otherwise
+    });
+    if (stdout) console.log(stdout.trim());
+    console.log(`[setu] ✓ Updated to ${latest}.`);
+  } catch (err) {
+    console.error(`[setu] Update failed: ${err.message}`);
+    console.error(`[setu] You can try running it yourself: npm install -g ${pkg.name}@${latest}`);
+    process.exit(1);
+  }
+}
+
+module.exports = { update };