@vmz/plugin 0.0.2 → 0.0.3

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.
Files changed (3) hide show
  1. package/README.md +7 -3
  2. package/index.js +0 -1
  3. package/package.json +2 -2
package/README.md CHANGED
@@ -44,10 +44,14 @@ compiler-visible boundaries.
44
44
 
45
45
  ## Why contribution beats mutation
46
46
 
47
- Mutation is convenient for the first plugin and expensive for the fiftieth. If every plugin can rewrite any source, graph node, or generated artifact, composition order becomes application semantics and no tool can explain the final result.
47
+ Mutation is convenient for the first plugin and expensive for the fiftieth. If every plugin can rewrite any source,
48
+ graph node, or generated artifact, composition order becomes application semantics and no tool can explain the final
49
+ result.
48
50
 
49
- A contribution says what capability is being added, which versioned schema it follows, what it reads, what it emits, and where it may execute. That extra structure is what allows npm extensibility and strong compilation to coexist.
51
+ A contribution says what capability is being added, which versioned schema it follows, what it reads, what it emits, and
52
+ where it may execute. That extra structure is what allows npm extensibility and strong compilation to coexist.
50
53
 
51
54
  ## The litmus test
52
55
 
53
- If installing the plugin makes `vmz check`, SSR, resume, tests, or deployment less able to explain the application, the integration is using the wrong boundary. A native plugin should leave VMZ more capable, not less coherent.
56
+ If installing the plugin makes `vmz check`, SSR, resume, tests, or deployment less able to explain the application, the
57
+ integration is using the wrong boundary. A native plugin should leave VMZ more capable, not less coherent.
package/index.js CHANGED
@@ -1,6 +1,5 @@
1
1
  /**
2
2
  * @vmz/plugin — protocol helpers (no N-API).
3
- * Design: 规划设计/vmz/14-Node-NAPI与插件宿主.md
4
3
  */
5
4
 
6
5
  import { createHash } from 'node:crypto';
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@vmz/plugin",
3
- "version": "0.0.2",
3
+ "version": "0.0.3",
4
4
  "type": "module",
5
5
  "description": "VMZ plugin protocol types and definePlugin / defineConfig helpers (no N-API)",
6
6
  "license": "MIT",
@@ -18,7 +18,7 @@
18
18
  "README.md"
19
19
  ],
20
20
  "dependencies": {
21
- "@vmz/protocol": "0.0.2"
21
+ "@vmz/protocol": "0.0.3"
22
22
  },
23
23
  "keywords": [
24
24
  "vmz",