@procedures/mongo 0.1.0 → 0.2.1

package/CHANGELOG.md

@@ -1,5 +1,34 @@
 # @procedures/mongo
 
+## 0.2.1
+
+### Patch Changes
+
+- Updated dependencies [a9dc8c8]
+  - @procedures/client@0.2.1
+  - @procedures/collections@0.2.1
+
+## 0.2.0
+
+### Minor Changes
+
+- 76d0d64: **Breaking:** an import of a package registers nothing. The `./register` entry of a package registers its procedures, and the procedures of the modules that they need, in the global registry (ARCHITECTURE-PROPOSALS-2026-10, P9).
+  
+  - `import "@procedures/git"` gives the exports and registers nothing. Use `import "@procedures/git/register"`, or give `gitModule` (`@procedures/git/module`) to `createRegistry()`.
+  - `import "@procedures/client/register"` registers the control flow (`client.chain` and the others) and `procedure.define`/`get`/`list`/`delete`. `createRegistry()` adds them to each new registry, as before. The new `registerClientProcedures(registry?)` does the same for any registry.
+  - Each `register<Name>Procedures(registry?)` function is in the module of its package, takes a registry (the global one by default) and registers the modules that the package requires. `registerBridge` (splay) and `register` (store) are now `registerSplayProcedures` and `registerStoreProcedures`. The old names stay for one version.
+  - `sideEffects` names only `./dist/register.js`, so a bundler can drop the rest of a package.
+  - The bundles require `clientModule`, so `@procedures/bundle-mcp/register` gives the whole tool surface.
+  - `lib new` makes `src/module.ts` and a root without side effects, and `procedure new` adds procedures to the module.
+
+### Patch Changes
+
+- Updated dependencies [0cf4bea]
+- Updated dependencies [44d3e30]
+- Updated dependencies [76d0d64]
+  - @procedures/client@0.2.0
+  - @procedures/collections@0.2.0
+
 ## 0.1.0
 
 The first release on npm. The packages of the client monorepo have one version together.

package/README.md

@@ -13,7 +13,7 @@ MongoDB client wrapper with client procedures for local or RPC access. Provides
 - **Local usage**: Direct MongoDB connection with native driver
 - **RPC usage**: Remote procedure calls via `client.call()`
 
-The package follows the client procedure pattern, auto-registering 16 procedures organized into 4 categories:
+The package follows the client procedure pattern, with 16 procedures in 4 categories. Its register entry (`import "@procedures/mongo/register"`) registers them:
 - **Database**: `ping`, `info`
 - **Collections**: `list`, `create`, `drop`, `stats`
 - **Documents**: `find`, `get`, `insert`, `update`, `delete`, `count`, `aggregate`
@@ -125,13 +125,10 @@ sequenceDiagram
 npm install @procedures/mongo
 ```
 
-### Peer Dependencies
+Since 0.2.0, an import of the package registers nothing. To register its procedures in the global registry:
 
-```json
-{
-  "@procedures/client": "github:mark1russell7/client#main",
-  "mongodb": "^7.0.0"
-}
+```ts
+import "@procedures/mongo/register";
 ```
 
 ## Configuration
@@ -1227,8 +1224,8 @@ await client.exec(
 
 ```typescript
 // In bundle-data/src/register.ts
-import "@procedures/mongo"; // registers its procedures
-import "@procedures/sqlite"; // registers its procedures
+import "@procedures/mongo/register"; // registers its procedures
+import "@procedures/sqlite/register"; // registers its procedures
 import "@procedures/s3/register.js";
 ```