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

iridium-bindings

v0.2.1

Published

TypeScript/WASM bindings for the Iridium GPU-accelerated text editor

Readme

iridium-bindings

The WebAssembly build of Iridium's editing kernel, plus the tree-sitter grammars it highlights with.

This is the engine, not the editor. Everything a browser needs on top of it — DOM events, the clipboard, the render loop, the public API — lives in @iridium-editor/core, which declares this package as a peer dependency. Install both; call the core.

npm install @iridium-editor/core iridium-bindings

What is inside

pkg/ is wasm-pack --target web output: iridium_bindings.js (the glue), iridium_bindings_bg.wasm (the kernel), and the matching .d.ts files. The module is the default export and must be initialised before use:

import init, { createWebEditor, sanitizePixelRatio } from "iridium-bindings";

await init();
const editor = await createWebEditor(canvas, sanitizePixelRatio(devicePixelRatio));

grammars/ holds the compiled tree-sitter grammars — C++, CSS, Go, HTML, JavaScript, JSON, Lua, Python, Rust, TOML, TSX, TypeScript and YAML — for hosts that want to load them directly rather than through @iridium-editor/core/syntax.

The kernel inside is the same Rust that runs the native desktop editor: the rope, the undo tree, multi-cursor editing, the keymap and chord resolver, the command registry and the palette's ranking. One implementation, several faces, so behaviour cannot drift between them.

Provenance

Every published tarball carries pkg/PROVENANCE.txt, naming the commit the wasm was built from, whether that tree was clean, and the rustc and wasm-pack versions that built it. The pkg/ directory is not committed to git, so this file is the only record connecting the bytes on npm to a revision of the source.

A note on the manifest

package.json also carries a napi block and a build script for @napi-rs/cli. That describes a Node native addon built from the same crate, which is not what this package publishes — main, types, exports and files all point at the wasm output. Splitting the two apart is tracked as issue #96; until then, treat the napi half as documentation of a sibling build, not of this artefact.

Licence

MIT. See LICENSE.