@gjsify/cli 0.23.0 → 0.24.1

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 CHANGED
@@ -30,12 +30,16 @@ npx @gjsify/cli info dist/index.js
30
30
  ## Native prebuilds
31
31
 
32
32
  Packages that ship compiled artifacts declare them with
33
- `"gjsify": { "prebuilds": "prebuilds", "platforms": ["linux-x86_64", "darwin-arm64", …] }`
33
+ `"gjsify": { "prebuilds": "prebuilds", "platforms": ["linux-x64", "darwin-arm64", …] }`
34
34
  and stage them under `prebuilds/<os>-<arch>/`. `run`, `info`, `tsc` and the bin launchers
35
- `install` writes all resolve that directory for the running host, accepting both spellings
36
- in use — uname-style (`linux-x86_64`, staged by the Vala/meson bridges) and node-style
37
- (`linux-x64`, `darwin-arm64`, `win32-x64`, staged by `@gjsify/node-gi` and `@gjsify/napi`) —
38
- and prefer whatever the package declares in `gjsify.platforms`.
35
+ `install` writes all resolve that directory for the running host.
36
+
37
+ There is ONE `<os>-<arch>` spelling: `${process.platform}-${process.arch}` — `linux-x64`,
38
+ `linux-arm64`, `darwin-arm64`, `win32-x64`. It is what a running process can compute about
39
+ itself, so resolution needs no translation. (`ppc64`, `s390x` and `riscv64` are spelled the
40
+ same in every vocabulary.) The resolver still probes a package's own `gjsify.platforms`
41
+ entry first, and falls back to the retired uname spelling (`linux-x86_64`), so a tarball
42
+ published before the rename keeps loading.
39
43
 
40
44
  The environment they export is `GI_TYPELIB_PATH` plus the library-search variable the host's
41
45
  dynamic loader actually reads: