19d01f0835
* fix(harness): start Pi sessions with MCP tools under Node The desktop app always gives Pi OpenPencil's MCP server, and the published companion failed every such session: - @ai-sdk/harness-pi imports pi-mcp-adapter, which publishes only TypeScript sources, and Node refuses to strip types under node_modules. A module load hook now strips them for TypeScript dependencies only; Bun runs them as is. (vercel/ai#22040) - pi-mcp-adapter imports @earendil-works/pi-tui but declares it as an optional peer, so npm leaves it out. The companion depends on it at the version pi-coding-agent uses, and a test keeps the two in step. (nicobailon/pi-mcp-adapter#805) - Pi reports live-process resume, yet the service handed it state saved by an earlier session, and the just-bash sandbox cannot resume, so every later session with that ID failed. Live-process backends now start fresh and drop saved state. Pi also installs the packages from a person's Pi settings with npm on every session, writing npm's output to the companion's stdout. The companion now keeps the real stdout for protocol messages, sends other writes to stderr, and quiets npm on success. The app logs companion stderr as diagnostics, since failures arrive as protocol errors. * fix(harness): reject another backend's state before dropping it loadResumeState removed saved state for a live-process backend before createSession checked which backend owned it, so state saved by another backend was lost instead of rejected. Ownership is checked first, and only state that belongs to the live-process backend is dropped.
31 lines
1.5 KiB
TypeScript
31 lines
1.5 KiB
TypeScript
import { describe, expect, test } from 'bun:test'
|
|
import { join } from 'node:path'
|
|
|
|
import harnessPackage from '../package.json'
|
|
|
|
function piTuiRange(manifest: unknown): string | undefined {
|
|
if (typeof manifest !== 'object' || manifest === null || !('dependencies' in manifest)) {
|
|
return undefined
|
|
}
|
|
const dependencies = manifest.dependencies
|
|
if (typeof dependencies !== 'object' || dependencies === null) return undefined
|
|
const range: unknown = Reflect.get(dependencies, '@earendil-works/pi-tui')
|
|
return typeof range === 'string' ? range : undefined
|
|
}
|
|
|
|
describe('Pi dependencies', () => {
|
|
test('pins pi-tui to the version pi-coding-agent uses', async () => {
|
|
// pi-mcp-adapter imports pi-tui but declares it as an optional peer, and pi-coding-agent nests
|
|
// its own copy, so the companion depends on pi-tui directly
|
|
// (https://github.com/nicobailon/pi-mcp-adapter/issues/805). Upgrading @ai-sdk/harness-pi
|
|
// moves pi-coding-agent; move this pin with it, or npm installs a second, mismatched pi-tui.
|
|
const harnessPi = Bun.resolveSync('@ai-sdk/harness-pi', join(import.meta.dir, '..'))
|
|
const agentManifest = Bun.resolveSync('@earendil-works/pi-coding-agent/package.json', harnessPi)
|
|
const manifest: unknown = await Bun.file(agentManifest).json()
|
|
const required = piTuiRange(manifest)
|
|
const pinned = harnessPackage.dependencies['@earendil-works/pi-tui']
|
|
expect(required).toBeString()
|
|
expect(Bun.semver.satisfies(pinned, required ?? '')).toBe(true)
|
|
})
|
|
})
|