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

@vaernjs/vaern

v0.0.6

Published

Vaern — an agent-native JavaScript & TypeScript runtime. Runs TypeScript directly, with fetch and an HTTP server built in.

Readme

vaern

An agent-native JavaScript & TypeScript runtime. Vaern runs TypeScript directly, with fetch and an HTTP server built in, on an embedded QuickJS-ng engine driven by Rust and Tokio. Capability sandboxing, tool-calling, MCP and replayable runs are being built into the engine itself.

VaernJS is a DevLogix project · licensed MIT


Status: v0.0.6, early native runtime

This release ships the native vaern binary for Linux, macOS and Windows. The API surface is small and will change before v1.0.

Works today

  • vaern run <file>: JavaScript and TypeScript, with types stripped at load time and line numbers kept
  • Relative ES module imports, and ES module packages already installed in node_modules
  • console, setTimeout / setInterval, queueMicrotask
  • process.argv, process.env, process.exit()
  • fetch with Headers, Response, AbortController, redirects and timeouts (hyper and rustls)
  • URL, URLSearchParams, TextEncoder and TextDecoder
  • serve() from vaern:http, an HTTP server with Web-standard Request / Response and streamed bodies
  • readFile, writeFile and appendFile from vaern:fs
  • Uncaught exceptions, unhandled rejections and throwing timers exit non-zero with a file:line:col location

Not implemented yet

  • node:* modules, CommonJS packages and downloading packages
  • Capability sandboxing (vaern.toml)
  • agent(), tool(), MCP, budgets and vaern replay

TypeScript enum, namespace and decorators are rejected with a located error, because they emit runtime code that type stripping cannot produce.


Install

npm install -g @vaernjs/vaern      # global CLI
npx @vaernjs/vaern --version       # without installing

npm installs one prebuilt binary for your platform through optionalDependencies, the same way esbuild does. Nothing is downloaded in a postinstall script; the platform packages are ordinary npm packages gated by os and cpu.

| Platform | Package | |---|---| | Linux x86_64 | @vaernjs/vaern-linux-x64 | | Linux arm64 | @vaernjs/vaern-linux-arm64 | | macOS arm64 | @vaernjs/vaern-darwin-arm64 | | macOS x86_64 | @vaernjs/vaern-darwin-x64 | | Windows x86_64 | @vaernjs/vaern-win32-x64 |

Linux binaries need glibc 2.35 or newer. On an unsupported platform, or when optional dependencies are skipped, vaern falls back to a small diagnostics CLI. Run vaern doctor there to see why.

Quick start

// latest.ts
interface Manifest {
  name: string;
  version: string;
}

const res = await fetch("https://registry.npmjs.org/@vaernjs/vaern/latest");
const pkg = (await res.json()) as Manifest;
console.log(`${pkg.name} ${pkg.version}, HTTP ${res.status}`);
vaern run latest.ts

Programmatic use

const { binaryPath, hasNativeBinary, vaern } = require("@vaernjs/vaern");

if (hasNativeBinary()) vaern(["run", "app.ts"]);

Links

  • Website: vaernjs.tech
  • DevLogix: devlogix.com.pk
  • Repository: github.com/vaernjs/vaern
  • Issues: github.com/vaernjs/vaern/issues
  • npm: @vaernjs/vaern

Licence

MIT License. Copyright (c) 2026 DEVLOGIX TECHNOLOGY (PRIVATE) LIMITED (DevLogix). See LICENSE.

Development

git clone https://github.com/vaernjs/vaern.git && cd vaern
cargo build --release
npm run check          # pre-publish validation
npm run pack:dry       # inspect exactly what would be published

Issues and pull requests welcome. We would rather be corrected now than wrong later.