# Install snapdir for Node.js

The `@snapdir/snapdir` package ships prebuilt native binaries, so you get the
full snapdir core — the same BLAKE3 walk, manifests, and 64-character snapshot
IDs as the CLI — with a single `npm install` and no compiler in sight.

<nav class="snapdir-lang" data-section="install" data-active="node" aria-label="Choose a language">
  <a href="/install/">CLI</a>
  <a href="/install/node/">Node.js</a>
  <a href="/install/python/">Python</a>
  <a href="/install/go/">Go</a>
  <a href="/install/java/">Java</a>
  <a href="/install/cpp/">C/C++</a>
  <a href="/install/zig/">Zig</a>
  <a href="/install/rust/">Rust</a>
</nav>
<script src="/assets/snapdir-lang.js" defer></script>

## Install

```sh
npm install @snapdir/snapdir
```

That is the whole install. The package is **prebuilt, zero build tools**: it
ships precompiled native binaries for Linux (glibc + musl) and macOS on x64 and
arm64, so there is no Rust toolchain, C compiler, or post-install build step.
The loader picks the right `.node` binary for your platform automatically —
including the musl build, which means it runs on **Alpine** out of the box. Each
release is CI-verified straight from npm on `node:22-alpine`.

## Platform support

Every binding runs on Linux (glibc and Alpine/musl, x64 and arm64) and macOS;
Windows is unsupported, since snapdir is Unix-only.

| Platform | Supported |
| --- | --- |
| Linux glibc (x64 + arm64) | yes |
| Linux musl / Alpine (x64 + arm64) | yes |
| macOS | yes |
| Windows | no |

The one binding-wide exception is **Java**, which is glibc-only today (musl
support is planned for 1.11.1). The Node.js binding has no such caveat — it
loads on glibc and musl alike.

## Next

- [Node.js quickstart](/quickstart/node/) — a 60-second push → pull round-trip.
- [snapdir for Node.js](/bindings/node/) — the full binding reference.