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

@hozo/compiler

v0.2.0

Published

JS-facing entry point for the Hozo Rust compiler (TSX analysis, Hozo IR, Web/Native lowering, diagnostics).

Readme

@hozo/compiler

The JS entry point to Hozo's Rust compiler. Every bundler integration goes through it; nothing else loads the native binding.

How the binding gets here

Development builds a debug addon next to src/:

pnpm --filter @hozo/compiler build:native

A release builds one npm package per platform, each carrying a release binary and declaring the os/cpu/libc it serves:

pnpm --filter @hozo/compiler pack:native                       # this machine
pnpm --filter @hozo/compiler pack:native -- --target <triple>  # a cross build

@hozo/compiler lists all eight as optional dependencies, which is what makes an install ship one binary instead of eight: npm evaluates each one against the machine, installs the match, and skips the rest without complaint.

The loader tries them in order — an adjacent development addon first, then the platform package — and HOZO_NATIVE_BINDING overrides both.

The list that must not drift

src/native-targets.ts is the one table. Two independent things read it: the packer, going from a Rust target triple, and native-loader.ts, going from process.platform/process.arch at runtime. A disagreement between them is invisible until someone on the platform nobody develops on installs a published package and is told no addon could be loaded for it, so native-targets.test.ts walks the table through both directions.

scripts/check-artifacts.mjs refuses a release that is missing any of the eight, for the same reason: an optional dependency that does not exist installs exactly as quietly as one that was skipped on purpose.

Release

.github/workflows/release.yml, on a v* tag. It has never run. It was written on a machine that can build one of the eight targets and cannot execute a workflow, so the musl and cross-architecture jobs in particular should be expected to need correcting on the first real attempt.


Part of Hozo, a Rust-powered universal UI compiler and accessibility-first layer for React Native. Most applications install @hozo/core and one build integration; see Getting started. Source and issues: github.com/iray-tno/hozo.