@procedures/procedure 0.1.0 → 0.2.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,32 @@
1
1
  # @procedures/procedure
2
2
 
3
+ ## 0.2.1
4
+
5
+ ### Patch Changes
6
+
7
+ - Updated dependencies [a9dc8c8]
8
+ - @procedures/client@0.2.1
9
+
10
+ ## 0.2.0
11
+
12
+ ### Minor Changes
13
+
14
+ - 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).
15
+
16
+ - `import "@procedures/git"` gives the exports and registers nothing. Use `import "@procedures/git/register"`, or give `gitModule` (`@procedures/git/module`) to `createRegistry()`.
17
+ - `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.
18
+ - 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.
19
+ - `sideEffects` names only `./dist/register.js`, so a bundler can drop the rest of a package.
20
+ - The bundles require `clientModule`, so `@procedures/bundle-mcp/register` gives the whole tool surface.
21
+ - `lib new` makes `src/module.ts` and a root without side effects, and `procedure new` adds procedures to the module.
22
+
23
+ ### Patch Changes
24
+
25
+ - Updated dependencies [0cf4bea]
26
+ - Updated dependencies [44d3e30]
27
+ - Updated dependencies [76d0d64]
28
+ - @procedures/client@0.2.0
29
+
3
30
  ## 0.1.0
4
31
 
5
32
  The first release on npm. The packages of the client monorepo have one version together.
package/README.md CHANGED
@@ -30,12 +30,16 @@ This package simplifies procedure development by automating the creation of proc
30
30
  ## Installation
31
31
 
32
32
  ```bash
33
- npm install github:mark1russell7/client-procedure#main
33
+ npm install @procedures/procedure
34
34
  ```
35
35
 
36
- **Dependencies:**
37
- - `@procedures/client` (peer dependency)
38
- - `zod` ^3.24.0
36
+ Since 0.2.0, an import of the package registers nothing. To register its procedures in the global registry:
37
+
38
+ ```ts
39
+ import "@procedures/procedure/register";
40
+ ```
41
+
42
+ npm installs its dependencies, `@procedures/client` and `zod`.
39
43
 
40
44
  ## Architecture
41
45
 
@@ -106,7 +110,7 @@ The scaffolded code compiles with the strict options of the workspace. A name wh
106
110
 
107
111
  ```typescript
108
112
  import { Client, LocalTransport, PROCEDURE_REGISTRY } from "@procedures/client";
109
- import "@procedures/procedure"; // registers its procedures
113
+ import "@procedures/procedure/register"; // registers its procedures
110
114
 
111
115
  const client = new Client(new LocalTransport({ registry: PROCEDURE_REGISTRY }));
112
116