中文
基于 v0.12.0..v0.12.1 的提交整理。
npm install -g @agegr/pi-web@latest修复
- 修复 pi 1.2.0 发布后安装 pi-web 无法启动:0.12.0 只固定了 pi 的四个包,而 pi 内部依赖用的是
^范围,所以 pi 1.2.0 发布后的新安装会把pi-coding-agent1.1.0 和pi-codemode1.2.0 装在一起,启动时报The requested module '@earendil-works/pi-codemode/declarations' does not provide an export named 'MCP_TYPESCRIPT_PREAMBLE'。现在依赖树里的每个 pi 包(包括pi-codemode、pi-mcp、pi-telemetry)都钉到精确版本,以后 pi 再发新版也不会混装。(35067b6) - 设置 › MCP:对提供资源(resources)的服务器点「测试」不再出错,改为显示「提供资源。」,和 pi 的
/mcp一致。(35067b6) - 配置了提供资源的 MCP 服务器时,发送消息不再白等 10 秒。(35067b6)
改进
- pi 升级到 1.2.0,变化见 pi v1.2.0 发布说明。(35067b6)
内部调整
- 新增测试:锁文件里的每个 pi 包都必须是精确版本的直接依赖。
- 发布 npm 包
@agegr/pi-web@0.12.1。
English
Prepared from commits in v0.12.0..v0.12.1.
npm install -g @agegr/pi-web@latestFixed
- pi-web failed to start when installed after pi 1.2.0 was released. 0.12.0 pinned only four of pi's packages, while pi's packages depend on each other with
^ranges, so fresh installs pairedpi-coding-agent1.1.0 withpi-codemode1.2.0 and the server failed withThe requested module '@earendil-works/pi-codemode/declarations' does not provide an export named 'MCP_TYPESCRIPT_PREAMBLE'. Every pi package in the tree (includingpi-codemode,pi-mcpandpi-telemetry) is now pinned to an exact version, so later pi releases cannot mix into an install. (35067b6) - Settings › MCP: Test no longer fails for a server that offers resources; it says "Offers resources.", as pi's
/mcpdoes. (35067b6) - A prompt no longer waits 10 s for a configured MCP server that offers resources. (35067b6)
Improved
- pi upgraded to 1.2.0; see the pi v1.2.0 release notes. (35067b6)
Internal
- A new test requires every pi package in the lockfile to be a direct dependency pinned to its exact version.
- Published npm package
@agegr/pi-web@0.12.1.