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

@treatjs/ant-sdk

v0.1.0-ant-sdk.33ae7017faf9

Published

Meta package for the Treat Ant native SDK. Installs the platform-specific prebuilt SDK for the current host.

Readme

@treatjs/ant-sdk

Meta package for the Treat Ant native SDK. If you don't know what treat or treat-ant-bridge is, stay tuned!

Versioning is <ABI>.ant-sdk.<ant commit hash>[.version]. ABI should match with your treat-ant-bridge crate version. Install the latest version of the ant sdk for your platform with:

"@treatjs/ant-sdk": "abi-0.1.0"

where 0.1.0 is your treat-ant-bridge version.

Installing this package pulls in the platform-specific prebuilt SDK for the current host via optionalDependencies:

| Package | Cargo target | | --- | --- | | @treatjs/ant-sdk-darwin-arm64 | aarch64-apple-darwin | | @treatjs/ant-sdk-darwin-x64 | x86_64-apple-darwin | | @treatjs/ant-sdk-linux-x64-gnu | x86_64-unknown-linux-gnu | | @treatjs/ant-sdk-linux-x64-musl | x86_64-unknown-linux-musl | | @treatjs/ant-sdk-linux-arm64-gnu | aarch64-unknown-linux-gnu | | @treatjs/ant-sdk-linux-arm64-musl | aarch64-unknown-linux-musl | | @treatjs/ant-sdk-win32-x64-gnu | x86_64-pc-windows-gnu (MinGW) |

Each platform package ships a sdk/ directory:

sdk/
  include/        treat_ant_bridge.h, ant.h, pkg.h
  lib/            libtreat_ant_bridge_helpers.a, libtreat_ant_native.a
  metadata/sdk.json
  LICENSES/

treat-ant-bridge's default build script locates this SDK automatically via node_modules/@treatjs/ant-sdk-<platform>, or explicitly via TREAT_ANT_SDK_PATH pointing at either the package directory or its sdk/ directory.

Releasing

Platform packages are produced by treat-ant-bridge/scripts/package_sdk.sh. The release process must:

  1. Fetch the pinned Ant source with scripts/fetch_ant_source.sh.
  2. Build Ant for the target (via the Nix/Meson flow or a cross toolchain).
  3. Run scripts/package_sdk.sh <out> --target <triple>.
  4. Copy the resulting sdk/ into the matching platform package directory.
  5. Populate sdk/LICENSES/ with notices for every bundled vendor dependency.
  6. Publish the platform packages, then the meta package.

See treat-ant-bridge/README.md for the full build model.