@telorun/analyzer 0.25.0 → 0.26.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.
package/README.md CHANGED
@@ -23,7 +23,7 @@ Built to be language-agnostic and infinitely extensible.
23
23
 
24
24
  ```bash
25
25
  # Reconcile your manifest into a running backend
26
- $ telo ./examples/hello-api.yaml
26
+ $ telo ./examples/hello-api
27
27
 
28
28
  {"level":30,"time":1771610393008,"pid":1310178,"hostname":"dev","msg":"Server listening at http://127.0.0.1:8844"}
29
29
  ```
@@ -1 +1 @@
1
- {"version":3,"file":"builtins.d.ts","sourceRoot":"","sources":["../src/builtins.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,kBAAkB,EAAE,MAAM,cAAc,CAAC;AAEvD,eAAO,MAAM,eAAe,EAAE,kBAAkB,EAud/C,CAAC"}
1
+ {"version":3,"file":"builtins.d.ts","sourceRoot":"","sources":["../src/builtins.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,kBAAkB,EAAE,MAAM,cAAc,CAAC;AAEvD,eAAO,MAAM,eAAe,EAAE,kBAAkB,EAwe/C,CAAC"}
package/dist/builtins.js CHANGED
@@ -298,6 +298,16 @@ export const KERNEL_BUILTINS = [
298
298
  type: "array",
299
299
  items: { type: "string" },
300
300
  },
301
+ // Files bundled alongside `telo.yaml` into the module's registry
302
+ // artifact (`module.tar.gz`) — static assets served by Http.Static,
303
+ // templates, etc. Ordered `.gitignore`-style patterns resolved against
304
+ // the manifest dir at publish time. Analyzer-only role: accept the
305
+ // field (the schema is additionalProperties:false); the analyzer never
306
+ // reads the assets. See kernel/nodejs/plans/bundle-controllers.md.
307
+ files: {
308
+ type: "array",
309
+ items: { type: "string" },
310
+ },
301
311
  // Inline imports — name-keyed map sugar for separate `Telo.Import`
302
312
  // documents. The key is the PascalCase alias (the import's
303
313
  // `metadata.name`). Each value is either a bare source string
@@ -422,6 +432,13 @@ export const KERNEL_BUILTINS = [
422
432
  type: "array",
423
433
  items: { type: "string" },
424
434
  },
435
+ // Files bundled into the module's registry artifact — same semantics as
436
+ // the Telo.Application `files` field above (a library may ship bundled
437
+ // templates, migrations, seed data).
438
+ files: {
439
+ type: "array",
440
+ items: { type: "string" },
441
+ },
425
442
  // Inline imports — same name-keyed map sugar as Telo.Application; the
426
443
  // loader desugars each entry into a synthetic Telo.Import. See the
427
444
  // Application schema above and analyzer/nodejs/src/inline-imports.ts.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@telorun/analyzer",
3
- "version": "0.25.0",
3
+ "version": "0.26.0",
4
4
  "description": "Telo Analyzer - Static manifest validator for Telo manifests.",
5
5
  "keywords": [
6
6
  "telo",
package/src/builtins.ts CHANGED
@@ -300,6 +300,16 @@ export const KERNEL_BUILTINS: ResourceDefinition[] = [
300
300
  type: "array",
301
301
  items: { type: "string" },
302
302
  },
303
+ // Files bundled alongside `telo.yaml` into the module's registry
304
+ // artifact (`module.tar.gz`) — static assets served by Http.Static,
305
+ // templates, etc. Ordered `.gitignore`-style patterns resolved against
306
+ // the manifest dir at publish time. Analyzer-only role: accept the
307
+ // field (the schema is additionalProperties:false); the analyzer never
308
+ // reads the assets. See kernel/nodejs/plans/bundle-controllers.md.
309
+ files: {
310
+ type: "array",
311
+ items: { type: "string" },
312
+ },
303
313
  // Inline imports — name-keyed map sugar for separate `Telo.Import`
304
314
  // documents. The key is the PascalCase alias (the import's
305
315
  // `metadata.name`). Each value is either a bare source string
@@ -424,6 +434,13 @@ export const KERNEL_BUILTINS: ResourceDefinition[] = [
424
434
  type: "array",
425
435
  items: { type: "string" },
426
436
  },
437
+ // Files bundled into the module's registry artifact — same semantics as
438
+ // the Telo.Application `files` field above (a library may ship bundled
439
+ // templates, migrations, seed data).
440
+ files: {
441
+ type: "array",
442
+ items: { type: "string" },
443
+ },
427
444
  // Inline imports — same name-keyed map sugar as Telo.Application; the
428
445
  // loader desugars each entry into a synthetic Telo.Import. See the
429
446
  // Application schema above and analyzer/nodejs/src/inline-imports.ts.