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

h5adexp

v0.1.17

Published

Single-file H5AD exploration service and LAN-friendly CLI

Readme

h5adexp

h5adexp is a single-file H5AD explorer. It starts a local Node.js service for one .h5ad file and serves the seqyuan React exploration UI, which can be opened directly on the LAN or embedded by another LAN web tool.

Quick LAN Explore

npm install -g h5adexp

h5adexp serve --file /path/to/sample.h5ad

The npm package and CLI command remain h5adexp; the browser UI brand shown in the top-left navbar is seqyuan.

By default the server listens on 0.0.0.0:3001. The CLI prints JSON containing:

  • url: a direct browser URL using this machine's LAN IP when available.
  • localUrl: a same-machine URL.
  • embedUrl: the compatibility URL with explicit token/query parameters.

Open url from another device on the same LAN. Opening http://<machine-ip>:3001/ also works because the app auto-loads the registered single file from /api/embed/config.

Options

h5adexp serve --file sample.h5ad --port 42317
h5adexp serve --file sample.h5ad --host 127.0.0.1
h5adexp serve --file sample.h5ad --host 0.0.0.0 --origin http://localhost:30141
  • --file <path>: required H5AD file.
  • --host <host>: default 0.0.0.0 for LAN access; use 127.0.0.1 for local-only access.
  • --port <port>: default 3001.
  • --runtime-home <dir>: runtime config/cache directory; defaults to a temporary isolated directory.
  • --origin <url>: iframe parent origin for integrations such as AnnoVibe.
  • --embed: accepted for compatibility; single-file mode enables embed config automatically.

h5adexp serve without --file is intentionally disabled. The product mode is one registered H5AD file per server process. Internal API and worker names may still contain projecthub because they are the stable remote compute layer, not a user-facing ProjectHub mode.

Build And Publish

npm install
npm run build:ci
npm run release:check
npm publish --access public

build/ and dist/ are generated artifacts. They are ignored by git but included in the npm package through package.json#files.

GitHub npm Release

The repository publishes to npm from tags named v<package.version>.

Required GitHub setup:

  • Environment: npm-publish
  • Repository secret: NPM_TOKEN, created from the npm account seqyuan

Release flow:

npm version patch --no-git-tag-version
npm run build:ci
npm run release:check
git add package.json package-lock.json README.md
VERSION=$(node -p "require('./package.json').version")
git commit -m "Release v${VERSION}"
git tag -a "v${VERSION}" -m "Release v${VERSION}" -m "Changes:" -m "- Summarize the release changes."
git push origin main --tags

Use an annotated tag and include the release notes in the tag message. The tag workflow verifies that the tag matches package.json#version, the tag commit is on main, and npm whoami for NPM_TOKEN is seqyuan.