@gjsify/node-runtime-win32-x64 0.44.0

package/LICENSE

@@ -0,0 +1,30 @@
+MIT License
+
+Copyright (c) 2026 gjsify contributors
+
+This license covers the SOURCE of this package (index.js, index.d.ts) and the
+fetch script in the gjsify repository that populates it. It does NOT cover the
+Node.js interpreter under `bin/`: that keeps the terms of the Node.js project
+and its bundled dependencies, reproduced verbatim in `bin/LICENSE` inside the
+published tarball.
+
+Node.js is a registered trademark of the OpenJS Foundation. This package is not
+affiliated with, endorsed, or sponsored by the OpenJS Foundation.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,126 @@
+# @gjsify/node-runtime-win32-x64
+
+The **Node.js interpreter for Windows x64**, packaged so an application built with
+gjsify can carry its own. Three files, nothing else:
+
+```
+bin/node.exe        the interpreter (93,381,448 B), verbatim from the pinned Node 24 LTS release
+bin/LICENSE         Node's own LICENSE, verbatim from that same release
+bin/manifest.json   which release, which URL, which digests
+```
+
+Platform-gated (`os: ["win32"]`, `cpu: ["x64"]`), tier 3. On any other
+platform `npm install` REFUSES it with `EBADPLATFORM` — see
+[Installing it from another platform](#installing-it-from-another-platform), which
+is not an edge case here. The `bin/` payload is **not committed** — it is fetched and
+digest-checked on a CI runner by
+[`../scripts/fetch-node-runtime.mjs`](../scripts/fetch-node-runtime.mjs) and reaches
+consumers through the published tarball.
+
+## Who installs it
+
+**Nobody adds it to `dependencies`.** It follows the same rule as
+`@gjsify/gtk-runtime-*` (see [docs/publishing.md](../../../docs/publishing.md)):
+resolved **by name** by whoever *ships* the application, with no
+`optionalDependencies` edge anywhere. Making a runtime bundle a dependency of the
+library that uses it was [#910](https://github.com/gjsify/gjsify/issues/910) — a
+from-source addon met a foreign GTK, produced wrong method entries and a 29-minute
+timeout, and it was reverted in #920.
+
+So for an app author the answer is: **nothing to add**. `gjsify ship` resolves
+`@gjsify/node-runtime-<target>` for the target it is packaging and stages
+`bin/node.exe` into the artifact. Overriding it is
+`GJSIFY_NODE_RUNTIME=/path/to/bin`.
+
+## Why only three targets, and not Linux
+
+**Linux gets no package.** A `.deb` or `.rpm` declares a dependency on the
+distribution's Node instead — `Depends: nodejs (>= 24)` and
+`Requires: nodejs(engine) >= 24` — exactly as a `--app gjs` package declares
+`gjs`. Every Linux distribution ships a Node; macOS and Windows do not, which is
+the whole reason these three exist.
+
+⚠️ The rpm spelling is **not** `nodejs >= 24`. Measured with `dnf repoquery` on
+Fedora 44: `nodejs` as a name is provided only by `nodejs22-1:22.23.1`, whose
+**Epoch 1** beats the `0:24` that a bare `>= 24` desugars to — so
+`--whatprovides 'nodejs >= 24'` answers **nodejs22**. `nodejs(engine)` carries no
+epoch and resolves correctly.
+
+## Why `bin/node.exe` and not the whole distribution
+
+The full release drags in npm's bundled `node_modules`, which adds **149 further
+LICENSE files** — 149 attribution obligations for code that is not being shipped.
+(Measured on v24.20.0 as archive entries whose basename matches `^licen[cs]e`
+**case-insensitively**: 150 in total, one of which is Node's own. The case rule is
+load-bearing, not decoration — `license`, `license.js` and `license.md` account
+for 8 of the 150, and reading the predicate as literal capitals answers 142. The
+count is the same in the win-x64 zip and in the darwin tarballs, so it is a
+property of the release and not of one archive.) An interpreter inside a `.app` or a Windows program
+directory needs the binary and the terms it travels under.
+
+Node's own `LICENSE`, verbatim from the release, discharges the whole set in one
+file: MIT, Apache-2.0 §4(a)/(b), BSD-3 clause 2, Unicode-3.0, zlib, Artistic-2.0
+(npm), BlueOak-1.0.0 (minimatch) and ISC. **Zero copyleft** in the shipped binary.
+OpenSSL is upstream 3.5.7 under **Apache-2.0 alone** — not quictls, not the dual
+licence — so there is no advertising clause and no "Eric Young" attribution to
+reproduce, and no bundled Apache component ships a `NOTICE`.
+
+## Two traps the fetcher exists to close
+
+1. **`https://nodejs.org/dist/<v>/win-x64/` carries no LICENSE.** That directory
+   holds `node.exe`, `node.lib` and debug symbols and nothing else — measured on
+   v24.20.0, where it is the ONLY per-target directory the release publishes
+   (`darwin-arm64/` and `darwin-x64/` are 404). So this trap is a Windows trap
+   and it is this package's: 93 MB with no unzip step is the convenient route,
+   and it is the one that drops the redistribution obligation with no error. The
+   fetcher only ever reads the `.zip`.
+2. **One release ships the licence twice, byte-different.** 157,609 B with LF (in
+   the tarballs) and 160,555 B with CRLF (in the zip) — 2,946 CR, one per line.
+   Any size or digest check must expect **both**, or it passes two targets and
+   fails the third for a reason that reads like a corrupt download.
+
+## Installing it from another platform
+
+`os`/`cpu` gating is what keeps this 90–125 MB package off machines that cannot
+run it — but the design also says a Windows or macOS artifact may be assembled on
+**Linux** (ADR 0024 § A1: the packers are pure JavaScript and run anywhere). Those
+two pull in opposite directions, and npm resolves it in gating's favour. Measured
+with npm 11.17.0 on Linux:
+
+| command | result |
+| --- | --- |
+| `npm install <pkg>` | `EBADPLATFORM`, exit 1 |
+| `npm install --os=win32 --cpu=x64 <pkg>` | `EBADPLATFORM`, exit 1 — the flags do **not** help |
+| `npm install --force <pkg>` | installs, **exit 0** |
+| `npm pack <pkg>` | downloads the tarball, **exit 0** |
+
+⚠️ Measured against **`@gjsify/gtk-runtime-win32-x64@0.44.0`** — a published
+package with the same `os`/`cpu` gating — because the `@gjsify/node-runtime-*`
+names are not on npm yet. Run verbatim against one of these today and npm answers
+`E404`, not `EBADPLATFORM`; the rows become reproducible for these names after the
+first publish. Until then the same four commands work against a locally packed
+tarball (`gjsify pack`).
+
+So a shipper cross-assembling on Linux uses `--force` (or `npm pack` plus an
+extraction, which needs no override at all). This is NOT the "npm silently skips
+a platform mismatch" behaviour — that applies to an `optionalDependencies` entry,
+and this package is deliberately never one (see *Who installs it* above).
+
+## Use it directly
+
+```js
+import { nodePath, isPresent, licensePath } from '@gjsify/node-runtime-win32-x64';
+
+if (isPresent) {
+    // copy `nodePath` into your artifact — and `licensePath` beside it.
+}
+```
+
+`binaryName` is a package constant, never derived from `process.platform`:
+assembling a Windows artifact on Linux is a supported path, and a derived name
+would look for the wrong file there.
+
+---
+
+Node.js is a registered trademark of the OpenJS Foundation. This package is not
+affiliated with, endorsed, or sponsored by the OpenJS Foundation.