@tiens.nguyen/gu-cli 1.0.686

package/node-version.mjs

@@ -0,0 +1,40 @@
+/**
+ * Refuse an unsupported Node version with a sentence someone can act on.
+ *
+ * package.json declares `engines: >=18`, but npm only WARNS about that and installs anyway —
+ * so the first sign of trouble is whatever happens to break first. Reported live on Node
+ * v16.13.1: the install "succeeded", then `gu` died on a module-resolution error that
+ * said nothing about Node at all.
+ *
+ * What actually needs 18: global `fetch` (18.0) and `AbortSignal.timeout()` (17.3). Both are
+ * used on the setup path, so the failure lands during a first run — the worst possible moment,
+ * on a machine the user has just started trusting.
+ *
+ * Checked at the TOP of both entry points, before any import that might itself fail.
+ */
+export const MIN_NODE_MAJOR = 18;
+
+/** The message for a too-old runtime, or "" when this one is fine. Pure, so it is testable. */
+export function nodeVersionProblem(version = process.version) {
+  const major = Number.parseInt(String(version).replace(/^v/, "").split(".")[0], 10);
+  if (!Number.isFinite(major) || major >= MIN_NODE_MAJOR) return "";
+  return (
+    `gu needs Node ${MIN_NODE_MAJOR} or newer — this is ${version}.\n` +
+    `  Node ${major} has no global fetch, which the setup and update paths rely on.\n` +
+    "\n" +
+    "  With nvm:      nvm install --lts && nvm alias default lts/*\n" +
+    "  With brew:     brew install node\n" +
+    "  Debian/Ubuntu: curl -fsSL https://deb.nodesource.com/setup_lts.x | sudo -E bash - && sudo apt install -y nodejs\n" +
+    "\n" +
+    "  Then reinstall: npm i -g @tiens.nguyen/gu-cli"
+  );
+}
+
+/** Print the problem and exit, or return quietly. */
+export function requireSupportedNode() {
+  const problem = nodeVersionProblem();
+  if (!problem) return;
+  // console.error, not the REPL's own writer: this runs before any of that exists.
+  console.error("\n" + problem + "\n");
+  process.exit(1);
+}