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

@tschk/crepuscularity-wasm

v0.1.3

Published

WASM build of the crepuscularity parser — .crepus, JSX, Svelte and Vue templates to View IR

Readme

@tschk/crepuscularity-wasm

The crepuscularity parser, compiled to WebAssembly. This is the same Rust code that backs the crepus CLI — not a reimplementation — so JavaScript consumers and native targets lower templates identically.

import { parseCrepus, IR_VERSION } from "@tschk/crepuscularity-wasm";

const ir = parseCrepus(`div flex flex-col gap-4\n  span text-lg\n    "hello"`);
// { version: 6, root: [ { kind: "stack", ... } ] }

Template variables are bound by passing a context object:

parseCrepus('span\n  "hello {name}"', { name: "Ada" });

Other syntaxes

parseTemplate picks a frontend from the filename, so .crepus, .jsx/.tsx, .svelte and .vue all compile to the same View IR:

import { parseTemplate } from "@tschk/crepuscularity-wasm";

parseTemplate('<div class="flex"><span>{t}</span></div>', "Panel.svelte");
parseTemplate("<template><div class=\"flex\">{{ t }}</div></template>", "Panel.vue");

These are first-party frontends: neither svelte nor vue is a dependency. They compile the template. A <script> block is extracted and its semantics — Svelte runes, Vue's composition API, stores, lifecycle — are not executed; expressions are evaluated by crepuscularity's own evaluator. A construct the shared AST cannot represent is a parse error rather than a silent drop.

View IR

parseCrepus returns a ViewIr, a versioned tree of ViewNodes. Every node carries the original template class tokens on style.classes, so web renderers can pass them straight through as className instead of re-deriving CSS from the lowered style hints.

Check IR_VERSION if you persist or transport IR — the schema is versioned and bumps on incompatible changes.

Building

Requires the wasm32-unknown-unknown target and a wasm-bindgen CLI matching the wasm-bindgen crate version.

./build.sh