You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+12-4Lines changed: 12 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -163,10 +163,18 @@ For Node.js projects, you can install via npm:
163
163
npm install arkilian
164
164
```
165
165
166
-
The package builds the native addon from source on install (requires a C
167
-
toolchain and libcurl development headers). Prebuilt binaries are not
168
-
published yet — CI produces them on releases, but the npm install path
169
-
currently compiles.
166
+
Prebuilt native addons (`.node`) for `linux-x64`, `linux-arm64` (glibc &
167
+
musl/Alpine), `darwin-x64`, `darwin-arm64`, and `win32-x64` are bundled
168
+
inside the npm package via [`prebuildify`](https://github.com/prebuild/prebuildify).
169
+
At runtime [`node-gyp-build`](https://github.com/prebuild/node-gyp-build)
170
+
selects the correct prebuild for your platform — **no C compiler, no
171
+
`libcurl-dev` headers, and no network download at install time**. This
172
+
makes `npm install arkilian` work on minimal Alpine containers, AWS
173
+
Lambda, and serverless environments that lack a build toolchain.
174
+
175
+
If no prebuilt binary matches your platform (e.g. a rare arch/libc
176
+
combination), the install script falls back to a source build via
177
+
`node-gyp`, which requires `gcc`/`clang` and `libcurl-dev`.
170
178
171
179
## System Constraints and Design Choices
172
180
Unlike complex distributed SQLite systems (e.g., LiteFS or rqlite), Arkilian embraces single-writer architectures partitioned by micro-datasets. It purposefully avoids:
0 commit comments