Skip to content

chore: migrate to devframe v0.6.0#179

Open
antfubot wants to merge 1 commit into
antfu:mainfrom
antfubot:goofy-canyons-tickle
Open

chore: migrate to devframe v0.6.0#179
antfubot wants to merge 1 commit into
antfu:mainfrom
antfubot:goofy-canyons-tickle

Conversation

@antfubot

Copy link
Copy Markdown

Bumps devframe from ^0.5.2 to ^0.6.0.

Why

devframe v0.6.0 promotes version, packageName, homepage, and description to required fields on DevframeDefinition (they're surfaced in hub UIs and diagnostics). Everything else in the v0.5 → v0.6 surface is additive (scopes, settings, OTP auth, route-based MCP), so no other call sites needed changes.

What

  • Bump the devframe catalog entry to ^0.6.0 and refresh the lockfile.
  • Populate the four newly-required definition fields in devframe.ts from the inspector's own package.json, so version stays in sync with releases automatically.

Verification

  • pnpm typecheck, pnpm lint, pnpm test (78 passing), and pnpm build all green.
  • Smoke-tested the built CLI (--help and build end-to-end), confirming the static RPC-dump pipeline (createHostContext, createH3DevframeHost, collectStaticRpcDump) still works.

This PR was created with the help of an agent.

devframe v0.6.0 makes `version`, `packageName`, `homepage`, and
`description` required on the devframe definition, so surface them from
the inspector's package.json.
@pkg-pr-new

pkg-pr-new Bot commented Jul 10, 2026

Copy link
Copy Markdown

Open in StackBlitz

npm i https://pkg.pr.new/node-modules-inspector@179
npm i https://pkg.pr.new/node-modules-tools@179

commit: a9e8c3d

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant