@runner-run/linux-arm64-gnu - npm Package Compare versions

Comparing version 0.17.0 to 0.18.0

runner.cjs

+#!/usr/bin/env node
+/**
+ * Standalone launcher shipped inside every `@runner-run/*` platform
+ * package. Resolves the prebuilt binary package-relative (`bin/runner`
+ * next to this file), so the platform package works on its own:
+ *
+ *   npx @runner-run/<platform> install -f task1 task2
+ *   npx --package=@runner-run/<platform> runner list
+ *
+ * The facade (`runner-run`) remains the right dependency for anything
+ * portable — this exists so a pinned platform package is still a
+ * functional CLI rather than dead weight. Same spawn semantics as the
+ * facade's launcher: inherited stdio, exit-code passthrough, and
+ * signal re-raise so `set -e` / Ctrl+C chaining behave.
+ */
+"use strict";
+
+const process = require("node:process");
+const { argv, exit, stderr } = process;
+const { spawnSync } = require("node:child_process");
+const { join } = require("node:path");
+
+const exe = process.platform === "win32" ? "runner.exe" : "runner";
+
+try {
+	const result = spawnSync(join(__dirname, "bin", exe), argv.slice(2), {
+		stdio: "inherit",
+		windowsHide: false,
+	});
+	if (result.error) throw result.error;
+	// Child died from a signal (SIGINT, SIGTERM, …). Re-raise it on
+	// ourselves so the parent shell sees `WIFSIGNALED` / exit code
+	// 128 + N instead of a generic 1.
+	if (result.signal) {
+		process.removeAllListeners(result.signal);
+		process.kill(process.pid, result.signal);
+	} else {
+		exit(result.status ?? 1);
+	}
+} catch (err) {
+	stderr.write(`runner: ${err instanceof Error ? err.message : String(err)}\n`);
+	exit(1);
+}

package.json

 {
   "name": "@runner-run/linux-arm64-gnu",
-  "version": "0.17.0",
-  "description": "Prebuilt runner + run aarch64-unknown-linux-gnu binaries for runner-run; selected automatically by npm, not for direct use.",
+  "version": "0.18.0",
+  "description": "Prebuilt runner + run aarch64-unknown-linux-gnu binaries for runner-run; selected automatically by npm, also runnable standalone via npx.",
   "keywords": [
@@ -14,5 +14,3 @@ "runner-run",
     "arm64",
-    [
-      "glibc"
-    ]
+    "glibc"
   ],
@@ -41,2 +39,5 @@ "license": "MIT",
   ],
+  "bin": {
+    "runner": "runner.cjs"
+  },
   "exports": {
@@ -49,4 +50,5 @@ "./package.json": "./package.json"
   "files": [
-    "bin/"
+    "bin/",
+    "runner.cjs"
   ]
 }

README.md

@@ -8,3 +8,3 @@ # @runner-run/linux-arm64-gnu
 
-No. Install the main package and npm picks the matching binary for your platform automatically:
+Usually not. Install the main package and npm picks the matching binary for your platform automatically:
 
@@ -18,7 +18,22 @@ ```sh
 finds these binaries with no postinstall step. Depending on it directly pins you to a single
-platform, so install `runner-run` instead.
+platform, so prefer `runner-run` for anything portable.
 
+## Standalone use
+
+The package is a working CLI in its own right — it ships a `runner` bin that launches
+the bundled binary, so on a matching machine it runs without the facade:
+
+```sh
+npx @runner-run/linux-arm64-gnu list
+npx @runner-run/linux-arm64-gnu install -f build test
+npx --package=@runner-run/linux-arm64-gnu runner run lint
+```
+
+Useful when you want a platform-pinned install (e.g. a locked-down CI image) without
+pulling the facade and its sibling platform packages into the resolution.
+
 ## Contents
 
 - `runner` and `run`: prebuilt native binaries under `bin/`.
+- `runner.cjs`: package-relative launcher backing the `runner` bin.
 - No dependencies, no install scripts, no network access.
@@ -25,0 +40,0 @@

New alerts

Deprecated

Maintenance

The maintainer of the package marked it as deprecated. This could indicate that a single version should not be used, or that the package is no longer maintained and any new vulnerabilities will not be fixed.

Shell access

Supply chain risk

This module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code.

Fixed alerts

Empty package

Supply chain risk

Package does not contain any code. It may be removed, is name squatting, or the result of a faulty package publish.

Improved metrics

Total package byte prevSize

8192052

1.09%

Number of package files

6

20%

Lines of code

40

Infinity%

Number of lines in readme file

45

50%

Worsened metrics

Number of medium maintenance alerts

1

Infinity%

No dependency changes