vercel-labs / vercel-labs/native
No binary found for darwin-x64
Open
Nobody has claimed this yet.
- Dominant language
- Zig
- Stars
- 7.7k
- Forks
- 314
- Avg merge
- 5h
- Merged PRs (30d)
- 13
Description
% zero-native init my_app --frontend next
Error: No binary found for darwin-x64
Expected: /Users/admin1/.nvm/versions/node/v24.15.0/lib/node_modules/zero-native/bin/zero-native-darwin-x64
Run "npm run build:native" to build for your platform,
or reinstall the package to trigger the postinstall download.
% npm run build:native
npm error code ENOENT
npm error syscall open
npm error path /Users/admin1/Downloads/projects/zero-native/package.json
npm error errno -2
npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '/Users/admin1/Downloads/projects/zero-native/package.json'
npm error enoent This is related to npm not being able to find a file.
npm error enoent
npm error A complete log of this run can be found in: /Users/admin1/.npm/_logs/2026-06-09T05_25_10_295Z-debug-0.log
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the zero-native init my_app --frontend next failure, then inspect the package installation/postinstall path and the npm run build:native entry point mentioned in the report. Determine why the darwin-x64 binary is absent or why the build command cannot locate package.json; done means the command finds or builds the platform binary without the reported errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, zig
- Domain
- build-system, cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100