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

@tropel/core-wasm

v0.6.0

Published

Tropel core tier for browser embedders (KnockPort): the dynamic-variable catalog (and later auth signing / import parse) compiled to wasm32-unknown-unknown. No QuickJS — see API_CLIENT_WEB_PAYLOAD.md §2.3 two-tier split.

Readme

@tropel/core-wasm

Tropel's core tier for browser embedders — the pure compute every API client page needs, compiled to wasm32-unknown-unknown with a wasm-bindgen surface. No QuickJS, no WASI, no scenario runner: that is the separate heavy tier (@tropel/runtime-wasm / tropel_web.wasm).

Today it ships the dynamic-variable catalog ({{$guid}}, {{$timestamp}}, {{$randomHexColor}}, 35+ variables — the same DynamicCatalog the native runner uses, so the website, the extension and the CLI can never drift). Next residents: auth signing, OpenAPI/Postman import parsing, declarative assertions.

Why it exists

API_CLIENT_WEB_PAYLOAD.md §2.3 (two-tier wasm):

core tier    variables · auth signing · import parse        ~450 KB raw
             NO QuickJS — loaded eagerly

script tier  QuickJS + sandbox + shims (tropel-web)          ~2.5 MB
             extension/native only (or loaded only when a
             request actually has scripts)

A website/web app always executes scripts in the browser's own JS engine (@tropel/shims) and hits APIs through a CORS relay — it never needs the QuickJS tier. See KnockPort's WEB_EXTENSION_RUNTIME_SPLIT.md.

Usage

import { initCoreWasm, resolveDynamicVariables, getPredefinedVariableNames } from "@tropel/core-wasm";

await initCoreWasm();                                    // app boot
const out = resolveDynamicVariables("id={{$guid}}");     // sync, wasm-backed
const names = getPredefinedVariableNames();              // for editor autocomplete

initCoreWasm accepts { wasmUrl } or { wasmBytes } (Node/tests); by default it fetches pkg/tropel_core_wasm_bg.wasm relative to the package. Until (or if) init succeeds, resolveDynamicVariables degrades to a passthrough — {{$…}} survive literal and nothing throws.

Building

bash scripts/build.sh        # cargo release-wasm → wasm-bindgen → wasm-opt -Oz → smoke → pack dry-run

Requires the wasm32-unknown-unknown target and a modern wasm-opt (npm binaryen; wasm-pack's pinned 171374efd61df962 predates reference-types and cannot parse the output). Rust tests live in the crate (cargo test -p tropel-core-wasm); the JS smoke test runs in Node: node smoke.mjs.

Size

465,677 B raw after wasm-opt -Oz --strip-debug (155 KB brotli, measured, 234,323 B headroom under the 700 KB gate). ✅MEAS