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

@perryts/perry

v0.5.923

Published

Native TypeScript compiler. Compiles TypeScript source directly to native executables via LLVM.

Readme

@perryts/perry

Native TypeScript compiler. Compiles TypeScript source code directly to native executables via LLVM — no VM, no JIT warmup, no Node at runtime.

Install

npm install -g @perryts/perry
# or one-shot
npx @perryts/perry compile hello.ts -o hello && ./hello

Installing picks the right prebuilt binary for your platform automatically — @perryts/perry declares per-platform packages as optionalDependencies and npm (≥8.12) selects the matching one based on os / cpu / libc.

Supported platforms

| Platform | Package | |---|---| | macOS arm64 (Apple Silicon) | @perryts/perry-darwin-arm64 | | macOS x64 (Intel) | @perryts/perry-darwin-x64 | | Linux x64 (glibc) | @perryts/perry-linux-x64 | | Linux arm64 (glibc) | @perryts/perry-linux-arm64 | | Linux x64 (musl / Alpine) | @perryts/perry-linux-x64-musl | | Linux arm64 (musl / Alpine) | @perryts/perry-linux-arm64-musl | | Windows x64 | @perryts/perry-win32-x64 |

Host requirements

Perry produces native binaries by linking its runtime and stdlib (shipped as static archives in the platform package) into your code. That link step uses your system C toolchain, so you need:

  • macOS — Xcode Command Line Tools (xcode-select --install)
  • Linuxgcc or clang (e.g. apt install build-essential on Debian/Ubuntu, apk add build-base on Alpine)
  • Windows — MSVC / Visual Studio Build Tools with the C++ workload

Node.js 16 or later is required for the wrapper itself.

Usage

perry compile file.ts -o out      # compile to native binary
perry --version                   # print version
perry --help                      # full CLI reference

Links

  • Repository: https://github.com/PerryTS/perry
  • Issues: https://github.com/PerryTS/perry/issues
  • Changelog: https://github.com/PerryTS/perry/blob/main/CHANGELOG.md