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

@arminmajerie/data-morph-wasm

v0.1.1

Published

WASM bindings for data-morph (DataMorph)

Readme

DataMorph WASM bindings

This folder contains a small wasm-bindgen adapter crate that exposes a JSON-only API for using DataMorph (data-morph) from JS/TS.

Exports

All exports return JSON strings of the form:

{ "ok": true, "value": "...", "context": { "payloadFormat": "json", "payload": {}, "attributes": {}, "variables": {}, "error": null } }
  • evaluate_script(script: string, contextJson: string) -> string
  • validate_script(script: string) -> string
  • definitions_with_scope_d(contextJson: string) -> string (requires metadata+internals enabled on the Rust side)
  • fn_metadata_json(includeStandardPackages: boolean) -> string

Context JSON schema

contextJson must be valid JSON (keys must be quoted):

{
  "payloadFormat": "json",
  "payload": { "any": "json" },
  "attributes": { "k": "v" },
  "variables": { "k": 123 },
  "error": null
}

Notes:

  • Unknown top-level keys are accepted and become additional scope variables.
  • attributes and variables must be JSON objects.
  • variables also accepts the alias key vars.
  • Header-driven input/output directives can read/write non-JSON formats; support is best-effort and may not cover all DataMorph edge-cases.

Build (wasm-pack)

  1. Install target + wasm-pack:
rustup target add wasm32-unknown-unknown
cargo install wasm-pack
  1. Build npm/bundler-friendly output-dev:
  • DEV
cd d:\Code\IntegrationBuilder\IntegrationBuilder\data-morph\wasm
wasm-pack build --target bundler --out-dir .\pkg-web --dev
wasm-pack build --release --target web --out-dir pkg-web -- --features production
  • PROD
Set-Location "d:\Code\IntegrationBuilder\IntegrationBuilder\data-morph\wasm"

wasm-pack build --release --target bundler --out-dir pkg-web -- --features production

or

wasm-pack build --release --target web --out-dir pkg-web -- --features production

The generated JS glue + .wasm will be in wasm/pkg/.

Quick smoke test (Node)

After building, you can do a minimal import test from any TS/JS project by importing the generated package. See ts/wasm-loader.ts for a minimal loader.