Design 38: point at ADR 0069's real file name
This commit is contained in:
@@ -164,7 +164,7 @@ wrote, `tools/list` on loopback answers as before, and the controller's verbs an
|
|||||||
This is the first live step, and it is reversible by re-assigning `mesh-console`.
|
This is the first live step, and it is reversible by re-assigning `mesh-console`.
|
||||||
|
|
||||||
*Decided 2026-10-02:* `mesh-tools` keeps its name as the module the TypeScript images come from, and
|
*Decided 2026-10-02:* `mesh-tools` keeps its name as the module the TypeScript images come from, and
|
||||||
`node-tools` is a second module in the same repository ([ADR 0069](../../02-DECISIONS/0069-a-module-is-a-repository-and-a-path-within-it.md))
|
`node-tools` is a second module in the same repository ([ADR 0069](../../02-DECISIONS/0069-a-module-is-a-repository-and-a-path.md))
|
||||||
rather than a rename — the thirty-five manifests that build `on` `mesh-tools` stay true. Three things
|
rather than a rename — the thirty-five manifests that build `on` `mesh-tools` stay true. Three things
|
||||||
WP3 found that the plan did not say: a TypeScript bundle must carry its dependencies and a
|
WP3 found that the plan did not say: a TypeScript bundle must carry its dependencies and a
|
||||||
`package.json` naming its files as ES modules, which the toolchain now copies in from its own image;
|
`package.json` naming its files as ES modules, which the toolchain now copies in from its own image;
|
||||||
|
|||||||
Reference in New Issue
Block a user