@miden-sdk/node-linux-x64-gnu 0.17.2 → 0.17.4
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/AGENTS.md +17 -11
- package/miden_client_web.node +2 -2
- package/package.json +4 -1
package/AGENTS.md
CHANGED
|
@@ -14,13 +14,14 @@ The SDK is `@miden-sdk/miden-sdk`. Its guide, which is the one you want, is at
|
|
|
14
14
|
|
|
15
15
|
## Why it is installed
|
|
16
16
|
|
|
17
|
-
`@miden-sdk/miden-sdk` lists the
|
|
18
|
-
|
|
19
|
-
|
|
20
|
-
|
|
17
|
+
`@miden-sdk/miden-sdk` lists the native packages as `optionalDependencies`, so
|
|
18
|
+
your package manager installs only the one matching the current platform and
|
|
19
|
+
silently skips the rest. On Node.js the SDK's loader resolves the binary in
|
|
20
|
+
this order:
|
|
21
21
|
|
|
22
22
|
1. `MIDEN_MODULE_PATH`, or an explicit `modulePath` option
|
|
23
|
-
2. the platform package for `linux-x64
|
|
23
|
+
2. the platform package for `linux-x64` on a glibc C library, which is this one
|
|
24
|
+
(on musl it picks `@miden-sdk/node-linux-x64-musl` instead)
|
|
24
25
|
3. the SDK's own `prebuilds/` directory
|
|
25
26
|
4. the repo `target/` directory, for local development
|
|
26
27
|
|
|
@@ -32,14 +33,19 @@ implementation.
|
|
|
32
33
|
Do not try to require this package directly, and do not add it to your
|
|
33
34
|
`dependencies` to force it. A failure here is almost always one of:
|
|
34
35
|
|
|
35
|
-
- **Platform mismatch.** The `os` and `
|
|
36
|
-
what make npm skip non-matching platforms. A
|
|
37
|
-
architecture and run on another gets no
|
|
38
|
-
platform, or set `MIDEN_MODULE_PATH` to a
|
|
36
|
+
- **Platform mismatch.** The `os`, `cpu` and `libc` fields in this
|
|
37
|
+
`package.json` are what make npm and pnpm skip non-matching platforms. A
|
|
38
|
+
container built on one architecture or C library and run on another gets no
|
|
39
|
+
binary. Install on the target platform, or set `MIDEN_MODULE_PATH` to a
|
|
40
|
+
binary you supply.
|
|
41
|
+
With npm, an install for Linux from another OS (`npm install --os=linux
|
|
42
|
+
--cpu=x64`) must also pass `--libc=glibc`; npm cannot detect the C library of
|
|
43
|
+
a foreign OS and otherwise skips this package.
|
|
39
44
|
- **`--no-optional`, or a lockfile pinned on another platform.** Optional
|
|
40
45
|
dependencies are how this is delivered; skipping them skips the binary.
|
|
41
|
-
- **musl rather than glibc.**
|
|
42
|
-
other musl distributions
|
|
46
|
+
- **musl rather than glibc.** This package links against glibc and does not
|
|
47
|
+
load on Alpine or other musl distributions. Those use
|
|
48
|
+
`@miden-sdk/node-linux-x64-musl`.
|
|
43
49
|
|
|
44
50
|
In the browser none of this applies: the browser build runs WASM and never
|
|
45
51
|
loads a native module.
|
package/miden_client_web.node
CHANGED
|
@@ -1,4 +1,4 @@
|
|
|
1
1
|
[diffend] Oversized file quarantined before diffing.
|
|
2
2
|
name: package/miden_client_web.node
|
|
3
|
-
size:
|
|
4
|
-
sha256:
|
|
3
|
+
size: 78370168 bytes
|
|
4
|
+
sha256: f22d33065b8bbc7a8b388eb9ff1d4daec9f72aa7223b4616bdbcfe44ad2f3c07
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@miden-sdk/node-linux-x64-gnu",
|
|
3
|
-
"version": "0.17.
|
|
3
|
+
"version": "0.17.4",
|
|
4
4
|
"description": "Miden Client SDK native module for Linux x64 (glibc)",
|
|
5
5
|
"os": [
|
|
6
6
|
"linux"
|
|
@@ -8,6 +8,9 @@
|
|
|
8
8
|
"cpu": [
|
|
9
9
|
"x64"
|
|
10
10
|
],
|
|
11
|
+
"libc": [
|
|
12
|
+
"glibc"
|
|
13
|
+
],
|
|
11
14
|
"main": "miden_client_web.node",
|
|
12
15
|
"files": [
|
|
13
16
|
"miden_client_web.node",
|