jb/harness-tools
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: use Gitea-compatible package scope

Browse Source
This commit is contained in:
jb
2026-09-01 17:53:50 -04:00
parent 118b5bee06
commit 72a1645fdb
51 changed files with 142 additions and 142 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/npm-packages.md
+9 -9
View File
@@ -2,7 +2,7 @@
The repository uses Bun workspaces under `extensions/*`. External dependency versions live in the root `package.json` catalog; repository-owned dependencies use `workspace:^`.
Publishable packages include the repository-native extensions plus the imported `@_jb/pi-interactive-subagents`, `@_jb/pi-native-hooks`, and `@_jb/pi-todo-herdr` snapshots. `config/imported-packages.json` records their source `main` commits; use `bun run imports:check` to detect upstream movement.
Publishable packages include the repository-native extensions plus the imported `@jbcode/pi-interactive-subagents`, `@jbcode/pi-native-hooks`, and `@jbcode/pi-todo-herdr` snapshots. `config/imported-packages.json` records their source `main` commits; use `bun run imports:check` to detect upstream movement.
## Install and verify
@@ -16,10 +16,10 @@ Use plain `bun install` when intentionally updating `bun.lock`.
## Registry configuration
The tracked `.npmrc` routes only the `@_jb` scope:
The tracked `.npmrc` routes only the `@jbcode` scope:
```ini
@_jb:registry=https://git.jb.codes/api/packages/jb/npm/
@jbcode:registry=https://git.jb.codes/api/packages/jb/npm/
```
Configure a Gitea personal access token with package permissions outside the repository:
@@ -40,7 +40,7 @@ bun pm pack --destination ../../dist
bun publish
```
Publish `@_jb/pi-shared` before a new version of any extension that depends on it. Gitea rejects republishing an existing name/version, so bump the changed package version first.
Publish `@jbcode/pi-shared` before a new version of any extension that depends on it. Gitea rejects republishing an existing name/version, so bump the changed package version first.
`extensions/workflow` is intentionally private until the `_workflows` reference dependencies are merged into that package. `extensions/_workflows` must not be published.
@@ -49,11 +49,11 @@ Publish `@_jb/pi-shared` before a new version of any extension that depends on i
After configuring the same scope and token in the npm configuration visible to Pi:
```bash
pi install npm:@_jb/pi-dictate
pi install npm:@_jb/pi-file-search
pi install npm:@_jb/pi-interactive-subagents
pi install npm:@_jb/pi-native-hooks
pi install npm:@_jb/pi-todo-herdr
pi install npm:@jbcode/pi-dictate
pi install npm:@jbcode/pi-file-search
pi install npm:@jbcode/pi-interactive-subagents
pi install npm:@jbcode/pi-native-hooks
pi install npm:@jbcode/pi-todo-herdr
```
Pi installs runtime dependencies from the same scoped registry. The repository's symlink-based development exposure remains controlled separately by `config/pi-links.json`.