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

@geoff4lf/cue-wasm

v1.4.5

Published

Cuelang WASM runtime for the browser.

Readme

@geoff4lf/cue-wasm

NPM Version CI Status License: MIT

Cuelang for the Modern Web. A "Gold Standard" WebAssembly runtime and tooling layer for Cuelang, designed for zero-config integration in Next.js, Browsers, and Node.js.


🚀 Key Features

  • Full CUE Engine: Authority-level Unification, Validation, and Export powered by the official Go CUE API.
  • Phased Loading: Lightweight Reader (5.2MB) for instant interactivity, warming up the full Engine (27.1MB) in the background.
  • Zero-Config CDN: Browser builds automatically fetch the WASM binary from jsDelivr—no manual file copying required.
  • Interactive Tooling: JS-native Workspace manager for multi-file projects, AST symbol extraction, and auto-formatting.
  • Next.js & React Ready: Built-in useCue hook with high-performance Web Worker and IndexedDB caching support.
  • Security Hardened: Strict WASM sandbox isolation with verified LFI protection.

📦 Installation

npm install @geoff4lf/cue-wasm

🎮 Performance Playground (Mission Control)

Test the phased loading architecture and caching performance in our Dockerized playground:

./examples/performance/run.sh

Then visit http://localhost:9876/examples/performance/

🛠 Usage

1. In React / Next.js (Recommended)

import { CueProvider, useCue } from '@geoff4lf/cue-wasm/react';

function App() {
  return (
    // useWorker enables phased loading, web workers, and indexedDB caching
    <CueProvider useWorker={true}>
      <Validator />
    </CueProvider>
  );
}

2. In Node.js / Plain JS

import { loadWasm, Workspace } from '@geoff4lf/cue-wasm';

async function run() {
  const cue = await loadWasm();
  const ws = new Workspace();

  ws.addFile('schema.cue', 'package main\n#User: { name: string }');
  ws.addFile('data.cue', 'package main\nuser: #User & { name: "Geoff" }', true);

  const res = await cue.unify(ws.getOverlay(), ws.getEntryPoints());
  console.log(JSON.parse(res));
}

📐 Architecture & Performance

To prevent accidental "bloat" in your JS bundles and achieve near-instant TTI, this library is split into two distinct layers:

  1. WASM Reader (~5.2MB raw / <1MB compressed): The lightweight syntax and formatting engine.
  2. WASM Engine (~27.1MB raw / ~6MB compressed): The authoritative evaluator.

For detailed optimization strategies (HTTP Preloading, Compression), see the Performance Guide.

🧪 Documentation & Examples

🛡 Security

This project adheres to strict security standards. The WASM runtime is isolated from the host filesystem. For more details, see SECURITY.md.

📄 License

MIT © Geoff Miller