@fabiofiorita/porcelain

中文文档
0.75.1发布于 2026/11/01MITES Module构建来源已验证

Review coding agents’ changes from a browser, Mac or phone

原始使用文档
文档目录3 节
  1. Quick start
  2. Background service
  3. Repository development

@fabiofiorita/porcelain (0.75.1)

The Porcelain review server and bundled web app for a plain Node installation.

Quick start

The host needs Node 24+, Git, and the file watcher supported on its platform:

npx @fabiofiorita/porcelain@latest serve

# Permit other devices on the local network to connect:
npx @fabiofiorita/porcelain@latest serve --lan

# Install this exact CLI version as a user service (Linux):
npx @fabiofiorita/porcelain@latest service install

# Update the installed service to the newest published version:
porcelain service update

State lives in ~/.porcelain/; pass --data-directory to keep it somewhere else. Use porcelain serve --help for all options.

Nothing can reach the server until you pair a device. On the machine running it, porcelain pair "Phone" --address <the address serve printed> prints a link that works once; open it on the device itself. The address must be one this server answers at, and the not-paired screen in the browser shows the whole command with that device's own origin already filled in. porcelain devices lists what is paired and porcelain revoke <id> ends it. Coding agents connect over MCP with porcelain mcp, which needs no credential: it reaches a local socket only a process on this machine can open.

Background service

porcelain service install|status|update|recover|uninstall manages a systemd user service on Linux. Install persists the invoked package version outside the npx cache and writes a porcelain command to ~/.local/bin that runs it; it prints how to add that folder to PATH when it is missing, and leaves alone a porcelain there that it did not write.

porcelain service update installs the newest published version through the same updater as Settings → Update, waits for it to finish and says whether it updated, was already current or failed. npx @fabiofiorita/porcelain@<version> service update installs that exact version instead.

porcelain share lan on shares the service on the local network and porcelain share shows how it is shared. Sharing is kept in the data directory, so it survives restarts and updates.

Updates stop the service and back up SQLite before the new runtime can migrate it. An older CLI refuses to replace a newer runtime unless service update --allow-downgrade is explicit. Uninstall removes the service, the runtime and the porcelain command while retaining data, configuration, logs and database backups. Run service commands as the regular user, never with sudo.

Repository development

pnpm build:package

# Inspect the exact publishable archive:
cd dist-porcelain && npm pack

dist-porcelain/ is generated from a completed web and server build. Do not edit it by hand.

版本与发布记录

@fabiofiorita/porcelain 共发布 39 个版本,首次发布于 2026/08/22;过去 12 个月发布了 39 个版本。最新版本附带 npm provenance 构建来源证明,可追溯到公开的 CI 构建记录。

版本发布日期距今
0.75.1latest2026/11/012 天前
0.75.02026/11/012 天前
0.74.02026/10/313 天前
0.73.02026/10/304 天前
0.72.02026/10/304 天前
0.71.12026/10/2112 天前

关于 @fabiofiorita/porcelain 的常见问题

@fabiofiorita/porcelain 是什么?

从浏览器、Mac或手机上查看编码代理的更改

如何安装 @fabiofiorita/porcelain?

在项目目录运行 npm install @fabiofiorita/porcelain,或使用 pnpm add / yarn add / bun add。它还提供命令行工具 porcelain,可以用 npx porcelain 直接运行。

@fabiofiorita/porcelain 支持 TypeScript 吗?

该包的 package.json 没有声明类型入口。需要类型提示时,可以在 npm 上查找社区维护的 @types/fabiofiorita__porcelain 是否存在。

@fabiofiorita/porcelain 支持 ESM 还是 CommonJS?

以 ES Module 形式发布,推荐使用 import 引入。在 CommonJS 项目中,Node.js 20.19+ / 22.12+ 可以直接 require() 不含顶层 await 的 ES Module,更早的版本需要改用动态 import()。

@fabiofiorita/porcelain 需要什么版本的 Node.js?

package.json 的 engines 字段要求 Node.js >=24.20.0 <25。版本不符时 npm 默认只给出警告,开启 engine-strict 后会拒绝安装。

@fabiofiorita/porcelain 可以商用吗?

@fabiofiorita/porcelain 使用 MIT 许可。宽松许可:允许商业使用、修改和再分发,通常只需在分发时保留原版权与许可声明。以上为概括,不构成法律意见,请以许可原文为准。

@fabiofiorita/porcelain 还在维护吗?

最新版本 0.75.1 发布于 2026/11/01(2 天前);至今共发布 39 个版本,其中过去 12 个月发布了 39 个;首次发布于 2026/08/22。发布频率只是参考信号:功能稳定的工具可能很少需要更新,建议结合源码仓库的 issue 和提交记录判断。