smashimo/oh-my-pi
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: forward parseArgs and CONFIG_DIR_NAME from the legacy pi shim

Browse Source 
Legacy pi extensions import both from the `@earendil-works/pi-coding-agent`
package root, which omp aliases to legacy-pi-coding-agent-shim.ts. `parseArgs`
lives in ../cli/args and CONFIG_DIR_NAME in @oh-my-pi/pi-utils, and neither is
reachable through `export * from "../index"`, so Bun's static export check
rejects such extensions during validation.

Same class of barrel gap as issues #5968 and #6583.
This commit is contained in:
Gy-Hu
2026-07-28 22:14:23 +08:00
parent f446b8a819
commit e404102acc
1 changed files with 8 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
packages/coding-agent/src/extensibility/legacy-pi-coding-agent-shim.ts
+8
View File
@@ -1378,6 +1378,14 @@ export function getPackageDir(): string {
// check during validation (issue #6583).
export { estimateTokens } from "@oh-my-pi/pi-agent-core/compaction";
// Same barrel gap for two more legacy package-root exports: pi re-exported the
// `CONFIG_DIR_NAME` constant and the CLI parser `parseArgs`. In omp
// `CONFIG_DIR_NAME` lives in `@oh-my-pi/pi-utils` and `parseArgs` in
// `../cli/args`, neither of which the barrel below forwards, so legacy
// extensions importing either fail Bun's static export check during validation.
export { CONFIG_DIR_NAME } from "@oh-my-pi/pi-utils";
export { parseArgs } from "../cli/args";
export * from "../index";
export { formatBytes as formatSize } from "../tools/render-utils";
export { copyToClipboard } from "../utils/clipboard";