Skip to content

Conversation

@owenizedd
Copy link
Owner

@owenizedd owenizedd commented Dec 6, 2025

Let's make bum available for npm via napi-rs📦 🥳

@owenizedd owenizedd changed the title feat: prepare for npm release feat: release bum for npm package 🎉 Dec 6, 2025
Changes:
- Download artifacts to 'artifacts/' dir instead of root
- Move artifacts to root before universal build
- Remove unnecessary file verification (napi universal will fail if files missing)
- Update Node version from 18 to 22
- Simplify output messages

This approach is cleaner and avoids hash collision issues.
The artifacts directory contains both hashed and non-hashed files.
Remove hashed files (bum.darwin-*-*.node) to ensure napi universal
only sees the clean files (bum.darwin-x64.node, bum.darwin-arm64.node).
Explicitly tell napi universal to look for binaries in current directory
with the -d . flag to ensure it finds the files correctly.
The napi artifacts command fails when it finds hashed files.
Remove all hashed .node files (pattern: *-*-*.node) before moving
artifacts to npm packages.

This ensures only clean files (bum.darwin-x64.node, etc.) are packaged.
Changes:
- Remove tags-ignore to allow version tags to trigger CI
- Add explicit tags pattern: v[0-9]+.[0-9]+.[0-9]+
- Add pull_request trigger for PR testing

Now both deploy.yml and ci.yml trigger on version tags.
This release adds npm support via NAPI-RS:
- Can now install via: npm install -g @owenizedd/bum
- Supports npx usage: npx @owenizedd/bum use 1.3.0
- Multi-platform binaries published to npm
- Original install.sh still works via GitHub Releases
@owenizedd owenizedd merged commit 1d51827 into main Dec 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants