unom/punktfunk-plugin-xbox
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Drop the @punktfunk/host dependency this plugin never imports #1

Merged
enricobuehler merged 1 commits from chore/drop-spurious-sdk-dep into main 2026-08-08 16:19:03 +00:00
Conversation 0 Commits 1 Files Changed 2
+5 -7
1 Commits
Author SHA1 Message Date
enricobuehler e846b4c0e5 fix(deps): drop the @punktfunk/host dependency this plugin never imports
CI / build (pull_request) Successful in 17s
Details
CI / publish (pull_request) Skipped
Details 
This plugin imports nothing from the SDK — everything it uses comes from
`@punktfunk/plugin-kit`, which already declares `@punktfunk/host` as a
peerDependency. Listing it here as a runtime dependency was redundant, and the
redundancy had a cost.

It is what stops an SDK fix from ever reaching an installed plugin. With the SDK
declared per-plugin, bun honours each plugin's own locked resolution and gives it a
PRIVATE NESTED COPY under `node_modules/@punktfunk/plugin-<x>/node_modules/`, which
then shadows the shared copy at the root of the operator's plugins tree. Measured on
a live host 2026-08-08: publishing `@punktfunk/host@0.1.3` — the release that lets a
library scanner register `category`, so it stays out of the console nav — reached the
tree root and still left five nested 0.1.2 copies, so every plugin kept importing the
old SDK and the fix appeared to do nothing.

Dropping it leaves the kit's peer range as the single source of truth, so there is one
hoisted copy that the host can actually keep current.

Nothing about the runtime changes: bun installs the kit's peer, and the SDK resolves
exactly as before — verified here (host 0.1.3 resolved, typecheck, tests, lint and
build all green).

Version bumped to 0.1.1; publishing is what carries the change to operators.
 2026-08-08 14:13:49 +02:00