ata compile CLI exits with code 137 (OOM) silently — no output, no error

[productdevbook]

Bug

The ata compile CLI command exits with code 137 (OOM kill) without producing any output file or error message — even with a tiny schema.

Reproduce

echo '{"type":"object","properties":{"x":{"type":"string"}}}' > /tmp/min.json
npx ata compile /tmp/min.json -o /tmp/min.mjs
echo "exit:$?"
ls -la /tmp/min.mjs

Result:

exit:137
ls: /tmp/min.mjs: No such file or directory

Environment

• ata-validator: 0.12.6 (just installed via bun add ata-validator)
• Node: v24.11.0
• macOS Darwin 25.4.0 (Apple Silicon)
• Plenty of RAM available

Expected

CLI should produce the standalone validator module file at the -o path, or print a clear error.

Notes

• npx ata --help works fine
• npx ata --version errors with unknown command "--version" (separate small issue)
• Calling Validator(schema).toStandaloneModule() directly from a Node script also exits with 137 silently, so the bug seems to be in the standalone module generator on Node v24

Workaround

Using runtime new Validator(schema) works fine for now — only pre-compile via CLI fails.

[mertcanaltin]

137 with a tiny schema rules out actual OOM, more likely a
native-addon load SIGKILL. a few asks before I dig in:

1. does npm install work where bun add fails?

   rm -rf node_modules && npm install ata-validator@0.13.2
   npx ata compile /tmp/min.json -o /tmp/min.mjs

2. does node -e "require('ata-validator')" alone exit 0
   or also 137?

3. ls node_modules/ata-validator/prebuilds/ — what's there?

4. anything in ~/Library/Logs/DiagnosticReports/node*.crash
   from one of the failed runs?

5. exact sw_vers + sysctl -n machdep.cpu.brand_string.

#23 has the same shape on macOS 26.4 + apple silicon, want to
rule out a common cause.