genesis-stack 1.1.5 → 1.1.6
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/README.md +16 -0
- package/package.json +1 -1
- package/stacks/pieces/nodejs.md +11 -0
package/README.md
CHANGED
|
@@ -68,3 +68,19 @@ project's complete reviewed section wins; a catalog upgrade never rewrites it.
|
|
|
68
68
|
Projects with different output ids or commands must review the proposal during
|
|
69
69
|
preparation. A project can omit estimates and use its host's generic starting
|
|
70
70
|
policy. Neither the catalog nor the project stores host observations or limits.
|
|
71
|
+
|
|
72
|
+
## Connected package default
|
|
73
|
+
|
|
74
|
+
Node proposes Vibe64's opaque `Connected development` section containing only
|
|
75
|
+
`- Default package type: \`npm\``. Vibe64 can inspect this default without treating
|
|
76
|
+
it as a prepared development recipe. The project must add its real source-map,
|
|
77
|
+
preparation and verification declarations before connected development can run;
|
|
78
|
+
no repositories or commands are inferred from selecting Node. A project-owned
|
|
79
|
+
section wins unchanged, including an explicit different default.
|
|
80
|
+
|
|
81
|
+
For an existing current-format project whose selected Node catalog gains this
|
|
82
|
+
proposal, Genesis reports `STACK_PROJECT_CONTRACTS_INCOMPLETE` if the project
|
|
83
|
+
section is missing. Explicitly reconcile the already-selected Stack with
|
|
84
|
+
`genesis stack add nodejs`, then review the materialized contract. Older project
|
|
85
|
+
formats use the normal `genesis migrate` workflow. Catalog updates never install
|
|
86
|
+
a hidden runtime default or rewrite an existing project section.
|
package/package.json
CHANGED
package/stacks/pieces/nodejs.md
CHANGED
|
@@ -31,6 +31,13 @@ Node.js package, command, module, dependency, and test conventions.
|
|
|
31
31
|
|
|
32
32
|
## Adoption
|
|
33
33
|
|
|
34
|
+
- The proposed `## Connected development` section declares Vibe64's default
|
|
35
|
+
connected package type, `npm`. It does not declare repositories or executable
|
|
36
|
+
preparation. When connected development is needed, preserve that default in
|
|
37
|
+
the complete project-owned section and declare the application's real source
|
|
38
|
+
map, preparation and verification commands. An explicit `custom` connection
|
|
39
|
+
uses its project-defined script instead of npm treatment. Do not invent a
|
|
40
|
+
working recipe from the component name.
|
|
34
41
|
- Identify the package manager from the lockfile and preserve the existing
|
|
35
42
|
module system, supported Node.js version, package entrypoints, and executable
|
|
36
43
|
commands.
|
|
@@ -63,6 +70,10 @@ Node.js package, command, module, dependency, and test conventions.
|
|
|
63
70
|
estimate for the same process tree. Host measurements and owner limits stay
|
|
64
71
|
in runtime-local state, not in this source contract.
|
|
65
72
|
|
|
73
|
+
## Connected development
|
|
74
|
+
|
|
75
|
+
- Default package type: `npm`
|
|
76
|
+
|
|
66
77
|
## Deslop
|
|
67
78
|
|
|
68
79
|
- Preserve the package's existing module system, package manager, public
|