wrangler 4.x

Use Wrangler ^4.0.0 programmatically from Node.js, while avoiding deprecated v3 APIs, accidental remote data access, and assumptions that the CLI or Worker runtime is available in a plain script.

For

wrangler@4.129.1

Verified

2026-09-07, 4 examples executed

Package

@modootoday/pmcp-wrangler@4.0.0

What it covers

• Scope
• Programmatic exports
• `createTestHarness`
• `unstable_dev`
• `getPlatformProxy`
• `experimental_generateTypes`
• `unstable_startWorker`
• CLI and build behavior
• v4 migration traps
• Local versus remote data
• What this skill does not cover

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 { strict as assert } from "node:assert/strict";
import {
  createTestHarness,
  experimental_generateTypes,
  getPlatformProxy,
  unstable_dev,
  unstable_startWorker,
} from "wrangler";

assert.equal(typeof createTestHarness, "function");
assert.equal(typeof experimental_generateTypes, "function");
assert.equal(typeof getPlatformProxy, "function");
assert.equal(typeof unstable_dev, "function");
assert.equal(typeof unstable_startWorker, "function");

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-wrangler

It installs as a dev dependency of your project, and the MCP server finds it there like any other skill.