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

@mutka-explorer/module

v2.1.0

Published

Types + the defineModule() helper for authoring Mutka modules — the SandboxModuleDef shape, the full typed host API, and command-id inference.

Readme

@mutka-explorer/module

Types + the defineModule() helper for authoring Mutka modules.

A Mutka module is a single self-contained ESM file that export defaults a module definition. It reaches the system only through the host object passed to setup(host), and every host.* call is checked against the permissions it declares.

This package is types plus one tiny runtime export: defineModule, an identity function (def => def). Everything else is types, erased at compile time. The only reason defineModule exists at runtime is type inference - it captures your commands[].ids so host.onCommand only accepts ids you declared (a typo or stale id is a compile error). A bundler inlines the call, so your built index.js stays import-free - exactly what Mutka loads.

Install

npm i -D @mutka-explorer/module

Usage

import { defineModule } from "@mutka-explorer/module";

export default defineModule({
  id: "you.hello",
  name: "Hello",
  version: "1.0.0",
  permissions: ["fs:read"],
  commands: [
    { id: "you.hello.count", label: "Count items", contextMenu: true, when: { selection: "any" } },
  ],
  setup(host) {
    host.onCommand("you.hello.count", async (snap) => {   // ✓ autocompleted from commands[]
      const items = await host.fs.readDir(snap.currentDirectory);
      host.log(`${items.length} items`);
    });
    // host.onCommand("you.hello.typo", …)   ← compile error: not a declared command id
  },
});

host is fully typed (host.fs, host.ui, host.net, host.dialog, …), as are permissions, when clauses, the declarative UINode tree, and FormSchema.

Prefer no runtime import at all? import type { SandboxModuleDef } from "@mutka-explorer/module" and annotate const mod: SandboxModuleDef<"you.hello.count"> = { … } - the generic param enforces the same command-id matching, purely in types.

Build to a single file

Mutka loads one ESM file with the default export intact. Bundle your TypeScript (and any pure-JS dependencies) down to one index.js, e.g. with tsup:

tsup src/index.ts --format esm --bundle

The module runs in a Web Worker with no DOM and no native network (fetch/XMLHttpRequest/WebSocket are blocked). Use host.net for HTTP. Pure-logic libraries bundle fine; DOM- or network-dependent ones do not.

What's exported

Types only: SandboxModuleDef, SandboxHostApi (the host), ModulePermission, SandboxCommand, SandboxOpenHandler, WhenClause, UINode, FormSchema, FileItem, HostSnapshot, the contribution shapes (panels, columns, status-bar, file icons, discovery sources), and their supporting types.

Versioning

The package version tracks the Mutka app release it was generated from, so the types always match a shipped host API. See the app's docs/ for the full module architecture.