fix(cli): add early Node.js version check wrapper

[7amed3li]

Adds an early Node.js version check.

Resolves #763

[changeset-bot]

⚠️ No Changeset found

Latest commit: d06b5e3

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[fraxken]

Hmm any specific reason why you forced on CommonJS instead of implementing the same in ESM?

[rupayon123]

I reviewed this after seeing #763. The early check itself makes sense, and CI is green.

On the CommonJS question: I think this can stay ESM without importing the heavy CLI entrypoint before the version check. For example, bin/check-and-run.js could use the package’s existing type: "module" setup:

#!/usr/bin/env node

import { createRequire } from "node:module";
import semver from "semver";

const require = createRequire(import.meta.url);
const manifest = require("../package.json");

const currentVersion = process.versions.node;
const requiredRange = manifest.engines.node;

if (!semver.satisfies(currentVersion, requiredRange)) {
  console.error(`\n  @nodesecure/cli requires Node.js ${requiredRange}.` +
    `\n  Current version: v${currentVersion}\n`);
  process.exit(1);
}

await import("./index.js");

That keeps the guard before bin/index.js and its transitive imports, but avoids adding a CJS wrapper in an ESM package.