vercel-labs / vercel-labs/dev3000
@d3k/darwin-arm64@0.0.177 not published to npm
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.6k
- Forks
- 99
- Avg merge
- 20m
- Merged PRs (30d)
- 1
Description
Bug
@d3k/darwin-arm64@0.0.177 is listed as an optional dependency of dev3000@0.0.177 but is not published to the npm registry.
Reproduction
npm view @d3k/darwin-arm64@0.0.177 version
# => E404: '@d3k/darwin-arm64@0.0.177' is not in this registry.
npm view @d3k/darwin-arm64 versions --json
# => (empty)
This causes both bun install -g dev3000 and npm install -g dev3000 to fail to install the native binary on macOS ARM64. The CLI then errors with:
Could not find @d3k/darwin-arm64 binary.
Workaround
Installing the previous version alongside works:
npm install -g dev3000 @d3k/darwin-arm64
# installs 0.0.176 of the native binary, which is compatible
Environment
- macOS ARM64 (Apple Silicon)
- Node v22.18.0
- npm 10.x / bun 1.3.14
- dev3000 0.0.177
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
Start by inspecting the package publication configuration and release workflow for dev3000 0.0.177, using the reported npm view commands to confirm the missing @d3k/darwin-arm64 package. Done when the version is available in the npm registry and both npm install -g dev3000 and bun install -g dev3000 install the macOS ARM64 binary.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- cli, release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100