@gjsify/node-runtime-win32-x64 0.46.0 → 0.47.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +4 -4
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -96,10 +96,10 @@ with npm 11.17.0 on Linux:
|
|
|
96
96
|
|
|
97
97
|
⚠️ Measured against **`@gjsify/gtk-runtime-win32-x64@0.44.0`** — a published
|
|
98
98
|
package with the same `os`/`cpu` gating — because the `@gjsify/node-runtime-*`
|
|
99
|
-
names
|
|
100
|
-
|
|
101
|
-
|
|
102
|
-
|
|
99
|
+
names were not yet on npm when the rows were taken. They are now — all three went
|
|
100
|
+
live at `0.44.0` on 2026-08-30 — so the rows are reproducible against THIS package
|
|
101
|
+
directly. The control is kept because it names what was actually run, not what is
|
|
102
|
+
runnable today.
|
|
103
103
|
|
|
104
104
|
So a shipper cross-assembling on Linux uses `--force` (or `npm pack` plus an
|
|
105
105
|
extraction, which needs no override at all). This is NOT the "npm silently skips
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@gjsify/node-runtime-win32-x64",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.47.0",
|
|
4
4
|
"description": "Bundled Node.js interpreter for Windows x64 — just the `node.exe` binary from a pinned Node 24 LTS release plus its LICENSE, for apps that `gjsify ship` packages where no system Node can be assumed. Platform-gated (win32/x64 only). Node.js is a registered trademark of the OpenJS Foundation; this package is not affiliated with, endorsed, or sponsored by the OpenJS Foundation.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"license": "SEE LICENSE IN bin/LICENSE",
|