@telorun/cli 0.79.0 → 0.80.0

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.
@@ -1,30 +1,9 @@
1
1
  /**
2
- * Finding `telo-workspace.yaml` on disk.
3
- *
4
- * Its LOCATION is a general anchor the directory workspace-relative paths are
5
- * measured from, and the outer bound on how far a walk-up may look — while its
6
- * `modules:` list is release scope. So the finder lives here rather than under
7
- * `release/`: `telo run` bounds its `.env` collection with the marker and must
8
- * not reach into the release namespace to do it, where `loadWorkspace` (which
9
- * parses `modules:` and throws when the file is absent) sits one import away.
10
- *
11
- * Parsing the file is the analyzer's (`release/workspace-config.ts`); finding it
12
- * is the Node half, and this is all of it.
2
+ * Finding `telo-workspace.yaml` on disk — re-exported from the kernel, which owns
3
+ * it because `resolveCacheRoot` anchors the `.telo` cache on the same marker and
4
+ * must answer without a CLI (a child kernel started through the runtime seam, a
5
+ * test harness). Two walks would eventually disagree about what "this repo" means
6
+ * for env collection and for the cache.
13
7
  */
14
- import { WORKSPACE_FILENAME } from "@telorun/analyzer";
15
- export { WORKSPACE_FILENAME };
16
- /**
17
- * Walk up from `from` looking for the marker. Returns the directory holding it,
18
- * or `undefined` — the file is optional. `telo release` requires one and reports
19
- * its absence; `telo run` reads `undefined` as "no parent lookup".
20
- *
21
- * `from` is resolved through symlinks first: a manifest reached through a linked
22
- * directory would otherwise walk the LINK's parents, miss a marker that is right
23
- * there in the real tree, and silently fall back to a narrower answer.
24
- */
25
- export declare function findWorkspaceRoot(from: string): string | undefined;
26
- /** `fs.realpathSync`, falling back to the input when the path does not exist —
27
- * a manifest path that is wrong is the caller's error to report, not this
28
- * helper's to convert into a different one. */
29
- export declare function realPath(target: string): string;
8
+ export { WORKSPACE_FILENAME, findWorkspaceRoot, realPath } from "@telorun/kernel";
30
9
  //# sourceMappingURL=workspace-marker.d.ts.map
@@ -1 +1 @@
1
- {"version":3,"file":"workspace-marker.d.ts","sourceRoot":"","sources":["../src/workspace-marker.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;GAYG;AAEH,OAAO,EAAE,kBAAkB,EAAE,MAAM,mBAAmB,CAAC;AAIvD,OAAO,EAAE,kBAAkB,EAAE,CAAC;AAE9B;;;;;;;;GAQG;AACH,wBAAgB,iBAAiB,CAAC,IAAI,EAAE,MAAM,GAAG,MAAM,GAAG,SAAS,CAQlE;AAED;;gDAEgD;AAChD,wBAAgB,QAAQ,CAAC,MAAM,EAAE,MAAM,GAAG,MAAM,CAM/C"}
1
+ {"version":3,"file":"workspace-marker.d.ts","sourceRoot":"","sources":["../src/workspace-marker.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAEH,OAAO,EAAE,kBAAkB,EAAE,iBAAiB,EAAE,QAAQ,EAAE,MAAM,iBAAiB,CAAC"}
@@ -1,49 +1,9 @@
1
1
  /**
2
- * Finding `telo-workspace.yaml` on disk.
3
- *
4
- * Its LOCATION is a general anchor the directory workspace-relative paths are
5
- * measured from, and the outer bound on how far a walk-up may look — while its
6
- * `modules:` list is release scope. So the finder lives here rather than under
7
- * `release/`: `telo run` bounds its `.env` collection with the marker and must
8
- * not reach into the release namespace to do it, where `loadWorkspace` (which
9
- * parses `modules:` and throws when the file is absent) sits one import away.
10
- *
11
- * Parsing the file is the analyzer's (`release/workspace-config.ts`); finding it
12
- * is the Node half, and this is all of it.
2
+ * Finding `telo-workspace.yaml` on disk — re-exported from the kernel, which owns
3
+ * it because `resolveCacheRoot` anchors the `.telo` cache on the same marker and
4
+ * must answer without a CLI (a child kernel started through the runtime seam, a
5
+ * test harness). Two walks would eventually disagree about what "this repo" means
6
+ * for env collection and for the cache.
13
7
  */
14
- import { WORKSPACE_FILENAME } from "@telorun/analyzer";
15
- import * as fs from "node:fs";
16
- import * as path from "node:path";
17
- export { WORKSPACE_FILENAME };
18
- /**
19
- * Walk up from `from` looking for the marker. Returns the directory holding it,
20
- * or `undefined` — the file is optional. `telo release` requires one and reports
21
- * its absence; `telo run` reads `undefined` as "no parent lookup".
22
- *
23
- * `from` is resolved through symlinks first: a manifest reached through a linked
24
- * directory would otherwise walk the LINK's parents, miss a marker that is right
25
- * there in the real tree, and silently fall back to a narrower answer.
26
- */
27
- export function findWorkspaceRoot(from) {
28
- let dir = realPath(path.resolve(from));
29
- for (;;) {
30
- if (fs.existsSync(path.join(dir, WORKSPACE_FILENAME)))
31
- return dir;
32
- const parent = path.dirname(dir);
33
- if (parent === dir)
34
- return undefined;
35
- dir = parent;
36
- }
37
- }
38
- /** `fs.realpathSync`, falling back to the input when the path does not exist —
39
- * a manifest path that is wrong is the caller's error to report, not this
40
- * helper's to convert into a different one. */
41
- export function realPath(target) {
42
- try {
43
- return fs.realpathSync(target);
44
- }
45
- catch {
46
- return target;
47
- }
48
- }
8
+ export { WORKSPACE_FILENAME, findWorkspaceRoot, realPath } from "@telorun/kernel";
49
9
  //# sourceMappingURL=workspace-marker.js.map
@@ -1 +1 @@
1
- {"version":3,"file":"workspace-marker.js","sourceRoot":"","sources":["../src/workspace-marker.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;GAYG;AAEH,OAAO,EAAE,kBAAkB,EAAE,MAAM,mBAAmB,CAAC;AACvD,OAAO,KAAK,EAAE,MAAM,SAAS,CAAC;AAC9B,OAAO,KAAK,IAAI,MAAM,WAAW,CAAC;AAElC,OAAO,EAAE,kBAAkB,EAAE,CAAC;AAE9B;;;;;;;;GAQG;AACH,MAAM,UAAU,iBAAiB,CAAC,IAAY;IAC5C,IAAI,GAAG,GAAG,QAAQ,CAAC,IAAI,CAAC,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC;IACvC,SAAS,CAAC;QACR,IAAI,EAAE,CAAC,UAAU,CAAC,IAAI,CAAC,IAAI,CAAC,GAAG,EAAE,kBAAkB,CAAC,CAAC;YAAE,OAAO,GAAG,CAAC;QAClE,MAAM,MAAM,GAAG,IAAI,CAAC,OAAO,CAAC,GAAG,CAAC,CAAC;QACjC,IAAI,MAAM,KAAK,GAAG;YAAE,OAAO,SAAS,CAAC;QACrC,GAAG,GAAG,MAAM,CAAC;IACf,CAAC;AACH,CAAC;AAED;;gDAEgD;AAChD,MAAM,UAAU,QAAQ,CAAC,MAAc;IACrC,IAAI,CAAC;QACH,OAAO,EAAE,CAAC,YAAY,CAAC,MAAM,CAAC,CAAC;IACjC,CAAC;IAAC,MAAM,CAAC;QACP,OAAO,MAAM,CAAC;IAChB,CAAC;AACH,CAAC"}
1
+ {"version":3,"file":"workspace-marker.js","sourceRoot":"","sources":["../src/workspace-marker.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAEH,OAAO,EAAE,kBAAkB,EAAE,iBAAiB,EAAE,QAAQ,EAAE,MAAM,iBAAiB,CAAC"}
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@telorun/cli",
3
- "version": "0.79.0",
3
+ "version": "0.80.0",
4
4
  "description": "Telo CLI - Command-line interface for the Telo runtime.",
5
5
  "keywords": [
6
6
  "telo",
@@ -34,11 +34,11 @@
34
34
  "dist"
35
35
  ],
36
36
  "dependencies": {
37
- "@telorun/analyzer": "0.63.0",
37
+ "@telorun/analyzer": "0.64.0",
38
38
  "@telorun/glob": "0.2.0",
39
- "@telorun/ide-support": "0.15.0",
40
- "@telorun/kernel": "0.79.0",
41
- "@telorun/sdk": "0.79.0",
39
+ "@telorun/ide-support": "0.16.0",
40
+ "@telorun/kernel": "0.80.0",
41
+ "@telorun/sdk": "0.80.0",
42
42
  "@telorun/templating": "0.16.0",
43
43
  "dotenv": "^17.4.0",
44
44
  "packageurl-js": "^2.0.1",