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

@microsandbox/types

v0.6.0

Published

Shared task and wire contract types for microsandbox, as TypeScript.

Readme

@microsandbox/types

Shared task and wire contract types for microsandbox, as TypeScript.

This package is the type-only mirror of the microsandbox-types Rust crate. It gives TypeScript consumers (the Node SDK, the cloud front end, and anything talking to the cloud API) the exact sandbox spec and cloud wire shapes the rest of microsandbox uses, so a SandboxSpec or CloudCreateSandboxRequest means the same thing on both sides of the wire.

It contains no runtime code. Every export is a type or interface; importing it adds nothing to your bundle.

Generated, Not Hand-Written

src/index.ts is generated from the Rust crate with ts-rs and carries a // @generated header. Do not edit it. To change a shape, edit the Rust type and regenerate from the repo root:

cargo run -p microsandbox-types --features ts --bin microsandbox-types-generate

Install

npm install @microsandbox/types

Usage

Import the shapes you need with import type:

import type {
  SandboxSpec,
  RootfsSource,
  CloudCreateSandboxRequest,
} from "@microsandbox/types";

const image: RootfsSource = { Oci: { reference: "python", upper_size_mib: null } };

const req: CloudCreateSandboxRequest = {
  name: "worker",
  image: "python",
  vcpus: 2,
  memory_mib: 1024,
  env: {},
  ephemeral: true,
};

Generated Shape Notes

The bindings follow ts-rs conventions, which mirror the Rust serde representation:

  • Rust enums become tagged unions or string literals. RootfsSource is { "Bind": string } | { "Oci": OciRootfsSource } | { "DiskImage": {...} }; lowercase enums like StatVirtualization are "strict" | "relaxed" | "off".
  • VolumeMount is internally tagged with a type field ("Bind" | "Named" | "Tmpfs" | "DiskImage").
  • Optional Rust fields are T | null; fields skipped when absent are ?: optional.
  • serde_json::Value is rendered as the JsonValue alias for the network subdocuments (policy, dns, tls, secrets, interface).

Build And Typecheck

npm run build       # tsc -> dist/
npm run typecheck   # tsc --noEmit