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

@tinyfiles/node

v0.1.1

Published

AT-1 (Atom Teleporter) verified-lossless decoder -- native Node N-API addon over the C ABI (all backends + codecs)

Readme

@tinyfiles/node — native Node binding (N-API)

A native Node addon over the AT-1 decoder C ABI. Unlike the WASM build, this path supports all backends (xz, zstd, stored) and all codecs (including qcolumnar), because it loads the full decoder shared library at runtime.

const at1 = require('@tinyfiles/node');
const original = at1.decode(at1Bytes);   // Buffer | Uint8Array -> Buffer
console.log(at1.version());

A clean npm i @tinyfiles/node needs no compiler: the launcher pulls in the matching prebuilt platform package @tinyfiles/node-<os>-<arch> (carrying the prebuilt at1_napi.node + the bundled decoder shared library) via optionalDependencies. The build steps below are only for local development.

The addon dlopens the decoder library at startup. Resolution order: AT1_DECODER_LIB env var → next to the package → ../../c_decoder/<lib> (at1decode.dll / libat1decode.so / libat1decode.dylib).

Build

The shared decoder library must exist first:

cd c_decoder && make                       # builds libat1decode.* (and the CLI)
# Windows/mingw: gcc -O2 -DAT1_NO_MAIN -shared -o at1decode.dll at1_decode.c -llzma -lzstd

Then build the addon:

npm install            # runs node-gyp rebuild
# or, if node-gyp can't find your VS install (standalone Build Tools not registered
# with vswhere), build with MSVC directly using the cached node headers/lib:
cmd /c build_msvc.cmd  # Windows fallback -> build/Release/at1_napi.node

Test

node test.js

Verified: decodes all 11 committed vectors byte-identically (every backend + codec, including xz and qcolumnar) plus a malformed-input rejection check — 12/12.

Why an addon that loads a shared lib instead of compiling the decoder in? It keeps the addon tiny and free of any link-time dependency on liblzma/libzstd — those ship inside the decoder library, which is built once with the normal C toolchain.