bun-types 1.x
Use bun-types as TypeScript declarations for Bun runtime APIs, while avoiding the common mistake of treating it as a runtime package. Covers the current @types/bun wrapper shape, explicit configuration for direct bun-types usage, and the Bun APIs described by the declarations.
- For
bun-types@1.4.2- Verified
- 2026-09-08, 2 examples executed
- Package
@modootoday/pmcp-bun-types@1.1.0
What it covers
- v1.0.0 installation and TypeScript configuration
- Runtime boundary
- The `bun` module
- SQLite
- Other declared entry points
- Common mistakes
- Not covered
One example from this skill
This is the skill's own text, not a summary of it. It runs: that is what verifying means here.
import type {} from "bun-types";
import { file, serve, write, which, dns } from "bun";
import assert from "node:assert/strict";
assert.equal(typeof file, "function");
assert.equal(typeof serve, "function");
assert.equal(typeof write, "function");
assert.equal(typeof which, "function");
assert.equal(typeof dns, "object");What it did in the sandbox
Verifying this skill meant installing the package and running code against it with no route out. Nothing was observed. The full ledger lists every package examined, including the ones that never became a skill.
Nothing observed is not a finding of safety. It means one run, under one policy, produced nothing to report.
Getting it
With a subscription:
npx -y @modootoday/pmcp login
npx -y @modootoday/pmcp install @modootoday/pmcp-bun-typesIt installs as a dev dependency of your project, and the MCP server finds it there like any other skill.