openclaw - 💡(How to fix) Fix Migrate @mariozechner/pi-* @0.73.0 → @earendil-works/pi-* @0.74.0 (deprecated upstream) [1 pull requests]

Summary

npm install -g openclaw@latest (and any fresh local install) currently emits deprecation warnings for 4 direct deps and 2 transitive deps. The 4 direct ones — all @mariozechner/pi-*@0.73.0 — have published successors at @earendil-works/pi-*@0.74.0 (clean maintainer transfer; same descriptions on npm, version bumped one minor).

Reproduction

Fresh install of OpenClaw 2026.5.7 (eeef486):

$ npm install -g openclaw@latest

npm warn deprecated [email protected]: Use your platform's native DOMException instead
npm warn deprecated @mariozechner/[email protected]: please use @earendil-works/pi-agent-core instead going forward
npm warn deprecated [email protected]: uuid@10 and below is no longer supported.  For ESM codebases, update to uuid@latest.  For CommonJS codebases, use uuid@11 (but be aware this version will likely be deprecated in 2028).
npm warn deprecated @mariozechner/[email protected]: please use @earendil-works/pi-tui instead going forward
npm warn deprecated @mariozechner/[email protected]: please use @earendil-works/pi-ai instead going forward
npm warn deprecated @mariozechner/[email protected]: please use @earendil-works/pi-coding-agent instead going forward

Reproduces on every fresh install / version bump.

Direct deps to migrate

OpenClaw 2026.5.7's package.json pins all 4 of these at 0.73.0:

Each successor exists on npm at v0.74.0 with the same description as the deprecated package. Looks like a clean fork / org transfer rather than a breaking rewrite.

Transitive (likely auto-resolve after the migration)

• [email protected] — pulled in via one of the pi-* packages. Latest is uuid@11.
• [email protected] — also transitive. Node has had native DOMException since 17.0.0; the shim is obsolete.

Both will probably resolve themselves once @earendil-works/pi-*@0.74.0 is in place (assuming the new maintainer cleaned those up internally). Worth re-checking the warning list post-bump.

Scope note (why this is an issue, not a drop-in PR)

A package.json edit alone is 4 lines, but a code-search across the repo shows ~418 source references to @mariozechner/pi-* (TS types, TUI components, extensions, auto-reply, docs). The full migration is a search-and-replace across the codebase plus whatever 0.73.0 → 0.74.0 API-delta handling is needed. That's larger than a comfortable drive-by PR — a maintainer-driven sweep with the test suite is the right shape.

I'm not opening a PR for that reason; happy to test a beta or RC build if/when one is cut.

Environment

• OpenClaw 2026.5.7 (eeef486)
• Reproduces on every npm install -g openclaw@latest regardless of host OS — the deprecation messages come from the npm registry, not from anything platform-specific.