OverviewFilesCommitsIssuesDocsReleasesPeers

holepunchto-deps commits / bf6cfe6

README: the repo had none, and its purpose was undiscoverable
A tree of 26 vendored @holepunchto packages with no explanation. What it actually is: the backing store for the forge npm registry -- pear-git/lib/routes/npm-registry.js resolves a scoped package by looking for a subdirectory here first, then falling back to that package own bare repo. Said so, listed the 26, noted keet-daemon is a submodule rather than a vendored copy, and recorded that commits bump the set as one matched group per Keet release because the packages are ABI-coupled. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
bf6cfe6f9bfcbb9eeed63df0f80235c24d3fa0b5
by plankatron <fleeky@gmail.com> · 2026-09-10T15:45:15.000Z

Changed files (1) +51 -0

README.md +51 -0
……@@ -0,0 +1,51 @@
1# holepunchto-deps
2
3Vendored `@holepunchto/*` packages, served by the forge as an **npm registry**.
4
5These are not published to npmjs. `pear-git`'s npm-registry route
6(`lib/routes/npm-registry.js`) resolves a package request by looking in this repo first — each
7scoped package is a **subdirectory** here — and falling back to that package's own bare repo
8(e.g. `keet-daemon.git`) if it is not found.
9
10So this repo is why `npm install @holepunchto/keet-core` works against the forge at all. Its
11contents are the resolution table.
12
13## What is here
14
1526 packages under `@holepunchto/`:
16
17```
18broadcast-call keet-core-schemas keet-registry
19emojis keet-debug-helper keet-registry-client
20hyperdiscovery keet-default-config keet-registry-schema
21hyperindex keet-editor keet-room-registry
22keet-call keet-editor-parser keet-rpc
23keet-core keet-indexing keet-store
24keet-core-api keet-link-preview keet-translations
25keet-core-hyperdb keet-media keet-unread-anchors
26 keet-push legacy-keet-core-schemas
27```
28
29Plus `keet-daemon`, which is a **submodule** (gitlink), not a vendored copy.
30
31## Versions move together
32
33Commits bump the set as a matched group against a Keet release, because the `@holepunchto/*`
34packages are ABI-coupled — `keet-core` and its schema packages have to agree. Recent history:
35
36```
37keet-core 4.18.3 + keet-call 10.4.0 + keet-push 4.3.1 (Keet 4.18.0)
38@holepunchto 4.16.5 → 4.17.3 era (Keet 4.17.2)
39```
40
41Bump the whole set to a single Keet release rather than one package at a time; a mismatched
42`keet-core` against older schemas is the failure this layout exists to make visible.
43
44## Updating
45
46Replace the package directories with the contents from the target Keet release, commit as one
47change naming that release, and push. The forge picks it up on the next `pgh repo scan`.
48
49## License
50
51Each vendored package carries its own upstream license. This repo declares none of its own.