Repository navigation
ARM64 Incompatibilies #119
Description
The @nanonets/graft CLI cannot be initialized on an ARM64 Linux platform due to a fundamental native module limitation.
What happened:
- npm install -g @nanonets/graft ✅ — Successfully installed (36 packages)
- Warnings about blocked install scripts (expected on this platform)
- graft init ❌ — Failed with native build error:
Error: No native build was found for platform=linux arch=arm64
runtime=node abi=147 uv=1 armv=8 libc=glibc node=26.6.0
- The tree-sitter native module (required by graft) has no pre-built binary for ARM64 Linux
- node-gyp cannot compile the C++ addon on this architecture
Why this happens: - @nanonets/graft uses tree-sitter for parsing source code into ASTs
- tree-sitter compiles native C++ addons via node-gyp
- ARM64 Linux lacks pre-built binaries in the npm registry for this combination
- node-gyp build fails at runtime when trying to require('tree-sitter')
Result: - No graft/ folder was created — the init step errored before any graph could be built
- 0 map files built — the process errored out during initialization
Activity
Frankie-Xu commentedon Aug 24, 2026
Diagnosis (linux/arm64
graft init/ native tree-sitter)Confirmed unclaimed; no existing PR targets #119. Failure is at
require("tree-sitter")on CLI load, notnpm installand notscripts/postinstall.mjs(that script is a one-line nudge and never throws).src/cli.ts→engine.ts→build.ts/source-files.ts→extract.ts, which statically importstree-sitterand the depth grammars. One missing.nodetakes down every command (init,build,check, statusline).Prebuild matrix (published tarballs)
tree-sitter@0.21.1(runtime)tree-sitter-python@0.21.0tree-sitter-typescript@0.23.2tree-sitter-go@0.23.4tree-sitter-java@0.23.5tree-sitter-php@0.23.12tree-sitter@0.22.4/0.25.1tree-sitter@0.25.0tree-sitter-python@0.25.0Reporter's
No native build was found for platform=linux arch=arm64(Node 26 / ABI 147, glibc) matches the missing platform directory, not an ABI mismatch.node-gyp-buildis N-API (prebuildify --napi); blocked install scripts are a red herring when the prebuild isn't in the tarball.Options
A. Version bump to
tree-sitter@0.25.1+tree-sitter-python@0.25.0would ship linux-arm64 prebuilds, but that's #40's ABI migration (0.21→0.25). #40 is still OPEN, CONFLICTING, last Ubuntu CI failed. Mixingtree-sitter@0.25with today'stree-sitter-typescript@0.23.2/ java / php is not a small bump.0.25.0also shipped with zero prebuilds, so the supply chain is not something we should treat as the only safety net. Alpine/musl and "no compiler" would still lose.B+C (proposed): keep native parsers when they load (darwin/linux-x64 unchanged). If
require("tree-sitter")(or a per-grammar require) throws, route depth extensions through the existing WASM breadth path (web-tree-sitter+tree-sitter-wasm, which already has typescript/tsx/javascript/python/go/java/php). Print one warning:native parser unavailable on this platform — falling back to WASM (reduced binding fidelity)Fidelity drop (not papered over): no
bindings/recvTypeprecision; call edges only if atags.scmexists (otherwise the walker emits symbols only).graft check/ statusline must not error.Will implement as a non-draft PR against
mainunless a maintainer prefers waiting on #40.fix(build): fall back to WASM grammars when native tree-sitter is una…