enricobuehlerandClaude Opus 5 78926be4ac fix(store): a plugin install lands in the plugins dir, not the nearest package.json above it ...

Installing any plugin from the console failed on a user's Fedora 44 host with

  plugin store job failed: @punktfunk/plugin-virtualhere is not present after install

while the same version installed fine on every box we tried. The difference turned
out to be a file in his home directory.

`bun add` does not install into its working directory. It walks UP to the nearest
ancestor `package.json` and installs into that tree. A fresh plugins dir has no
`package.json` — the store and the runner only write `bunfig.toml` — so any stray
one above it captures the install: the packages land in `~/node_modules`, the
dependency is written to `~/package.json`, bun prints "installed …" and exits 0,
and the plugins dir stays empty. The plugins-dir `bunfig.toml` is not read in that
case either, so the outcome splits on whether `@punktfunk` resolves in the hijacked
tree: with no scope mapping there it 404s against npmjs and exits 1 ("the plugin
runner exited with status 1"); with one, it succeeds into the wrong tree and the
job dies on the presence check instead. Only the second shape looks like a broken
store, which is why this took a reproduction to find.

Seed the plugins dir with a `package.json` so it owns bun's install root. Three
call sites rather than one: the store job, the `plugins add` CLI, and the SDK's
`ensurePluginsDir`. The runner ships as its own package and can predate the host
binary, so the host cannot delegate this — the same reason `ensure_bunfig_scope`
writes the registry mapping on this side rather than passing a runner flag.

Seeding only ever touches a tree with no `node_modules`. A dir with packages and
no `package.json` is the hand-assembled/older layout that `installed_packages`
deliberately falls back to the naming convention for, and dropping an empty
`dependencies` on it reports every plugin the operator runs as uninstalled —
already pinned by `an_emptied_dependency_list_means_nothing_is_installed`.

The residual failure stops dead-ending: if the presence check fails anyway, the
error names the capturing ancestor and what to do about it.

Reproduced and fixed on glass (Nobara 44 VM, host + runner 0.22.3): with a stray
~/package.json the store reproduces the field report byte for byte — same 150 ms,
same phase sequence, same message — and with the plugins dir seeded the same
install lands correctly with nothing leaking into the home dir.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-07-31 12:48:25 +02:00

..

api.test.ts

feat(sdk): Effect v4 + @effect/openapi-generator; typed pf.api & example ladder

2026-07-17 12:40:04 +02:00

config.test.ts

feat(security): add a user-writable plugin ingest inbox for cross-account data

2026-07-20 00:45:27 +02:00

plugins.test.ts

fix(store): a plugin install lands in the plugins dir, not the nearest package.json above it

2026-07-31 12:48:25 +02:00

runner-cli.test.ts

fix(scripting): park the idle runner instead of pinning a core

2026-07-25 15:13:11 +02:00

runner.test.ts

feat(store): console plugin store, index repo, and the fixes on-glass found

2026-07-20 20:48:02 +02:00

sse.test.ts

feat(sdk): @punktfunk/host — the Effect TypeScript SDK (M3)

2026-07-17 00:14:39 +02:00

surfaces.test.ts

feat(sdk): @punktfunk/host — the Effect TypeScript SDK (M3)

2026-07-17 00:14:39 +02:00

ui.test.ts

feat(plugins): console-hosted plugin UI surface (host registry + SDK servePluginUi + console proxy/nav)

2026-07-18 09:48:37 +02:00

wire.test.ts

feat(sdk): Effect v4 + @effect/openapi-generator; typed pf.api & example ladder

2026-07-17 12:40:04 +02:00