npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@hakobu/hakobu

v1.0.1

Published

Package your Node.js project into an executable

Downloads

148

Readme

@hakobu/hakobu

The modern Node.js packager — the successor to @yao-pkg/pkg. Package your Node.js project into a standalone executable that runs without Node.js installed.

Install

npm install @hakobu/hakobu --save-dev

Or globally:

npm install -g @hakobu/hakobu

Quick Start

# Package the current project
npx @hakobu/hakobu .

# Package with a specific target
npx @hakobu/hakobu . --target node24-linux-x64

# Multi-target build
npx @hakobu/hakobu . --target node24-linux-x64,node24-macos-arm64,node24-win-x64

CLI Usage

hakobu <project-root> [options]

Commands:
  hakobu <project-root>                Package a project
  hakobu targets                       Show available targets and cache
  hakobu inspect <project-root>        Analyze a project without packaging
  hakobu doctor <project-root>         Check if a project is ready to package

Options:
  --target <spec>       Target(s), comma-separated. Use 'all' for all published targets
  --output <path>       Output executable path
  --entry <file>        Entry file (relative to project root)
  --debug, -d           Show detailed packaging diagnostics
  --help, -h            Show help
  --version, -v         Show version

Bundle Mode:
  --bundle [name]       Pre-bundle with Rolldown before packaging
  --external <mod>      Keep module external when bundling (repeatable)

Advanced:
  --bytecode            Compile JS to V8 bytecode before packaging
  --compress <algo>     Compress snapshot (Brotli or GZip)
  --options <flags>     Bake V8 flags into executable (comma-separated)
  --build, -b           Force local build of base binary

Targets

Target format: node24-{platform}-{arch}

| Target | Tier | |---|---| | node24-linux-x64 | 1 | | node24-linux-arm64 | 1 | | node24-win-x64 | 1 | | node24-macos-arm64 | 1 | | node24-macos-x64 | 2 | | node24-linuxstatic-x64 | 2 | | node24-win-arm64 | 2 |

Use --target all to build for all published targets.

Configuration

Configure via the "hakobu" field in package.json:

{
  "hakobu": {
    "entry": "src/index.js",
    "assets": ["templates/**", "views/**"],
    "target": "node24-linux-x64",
    "output": "dist/my-app"
  }
}

The legacy "pkg" field is accepted with migration warnings. CLI flags override package.json config.

Bundle Mode

For TypeScript and monorepo projects, use --bundle to pre-bundle with Rolldown before packaging:

npx @hakobu/hakobu . --bundle --entry src/cli.ts --external electron

See Bundle Mode documentation for details.

Platform Features

macOS Signing & Notarization

npx @hakobu/hakobu . --target node24-macos-arm64 \
  --sign-identity "Developer ID Application: ..." \
  --notarize

macOS App Bundle

npx @hakobu/hakobu . --target node24-macos-arm64 \
  --app-bundle --bundle-id com.example.my-app

Windows PE Metadata

npx @hakobu/hakobu . --target node24-win-x64 \
  --product-name "My App" \
  --company-name "My Company" \
  --file-version 1.0.0 \
  --icon app.ico

Linux AppDir / AppImage

npx @hakobu/hakobu . --target node24-linux-x64 \
  --appdir --desktop-name "My App"

npx @hakobu/hakobu . --target node24-linux-x64 \
  --appimage --desktop-name "My App"

Programmatic API

import { exec } from '@hakobu/hakobu';

await exec(['.', '--target', 'node24-linux-x64', '--output', 'dist/app']);

Migrating from @yao-pkg/pkg

npm uninstall @yao-pkg/pkg
npm install @hakobu/hakobu --save-dev

Rename the "pkg" field to "hakobu" in your package.json. The legacy "pkg" field still works with migration warnings.

See the Migration Guide for full details.

Documentation

License

MIT