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

@vela-rbxts/compiler-wasm

v0.13.1

Published

WebAssembly build of the vela-rbxts compiler, for hosts that cannot load the native addon.

Readme

@vela-rbxts/compiler-wasm

WebAssembly build of the vela-rbxts compiler.

Same crate as @vela-rbxts/compiler, compiled to wasm32-unknown-unknown instead of a native N-API addon, so className lowering can run somewhere the platform binary cannot be loaded — a browser, most notably. The docs site's playground uses it to lower what you type with the real compiler rather than an imitation of it.

Build tooling should keep using @vela-rbxts/compiler: the native addon is faster, and rbxtsc runs on Node.

Only transform is exposed. The editor APIs the LSP uses (completions, hover, diagnostics, document colors) are native-only.

Usage

The module is a wasm-pack web target build: the wasm has to be instantiated before any export is called.

import init, { transform } from "@vela-rbxts/compiler-wasm";
// Bundler-resolved URL for the payload. Vite, webpack and friends emit it as
// an asset; without a bundler, point this at wherever you serve the file from.
import wasmUrl from "@vela-rbxts/compiler-wasm/vela_compiler_bg.wasm?url";

await init({ module_or_path: wasmUrl });

const result = transform(`<frame className="p-4 bg-slate-800" />`, {
  // Optional: a *resolved* config, as `defineConfig` from
  // `@vela-rbxts/config` returns it. Omitted means the built-in defaults.
  configJson: undefined,
});

result.code; // lowered source
result.diagnostics; // [{ level, code, message, token, range }]

License

MIT