@theholocron/cli 5.0.0-alpha.341 → 5.0.0-alpha.342
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 +8 -7
- package/dist/cli.mjs +192 -396
- package/dist/cli.mjs.map +1 -1
- package/dist/{compose-BucaYv2k.mjs → config-system-Bq6510iF.mjs} +30 -8
- package/dist/{index-BfArEnkX.d.mts → config-system-uaeB3g1g.d.mts} +22 -3
- package/dist/index.d.mts +2 -22
- package/dist/index.mjs +1 -30
- package/dist/presets.d.mts +1 -1
- package/dist/presets.mjs +1 -1
- package/package.json +11 -11
package/README.md
CHANGED
|
@@ -754,8 +754,8 @@ export default defineConfig({
|
|
|
754
754
|
|
|
755
755
|
Each SDK sits behind an interface from `@theholocron/observability` —
|
|
756
756
|
`ErrorSink` (Sentry) / `AnalyticsSink` (PostHog); the adapters, and the only
|
|
757
|
-
`@sentry/node` / `posthog-node` imports, live in that package. `observability
|
|
758
|
-
|
|
757
|
+
`@sentry/node` / `posthog-node` imports, live in that package. the orchestration is `createCliTelemetry` in `@theholocron/kyber/observability`;
|
|
758
|
+
`observability/telemetry.ts` binds it to the Holocron-specific credential resolution
|
|
759
759
|
(`observability/resolve-telemetry.ts`). See the
|
|
760
760
|
[telemetry guide](https://docs.theholocron.dev/holocron/telemetry/).
|
|
761
761
|
|
|
@@ -790,9 +790,10 @@ the local override exists to exempt.
|
|
|
790
790
|
providers implement
|
|
791
791
|
- `src/config.ts` — config schema, `defineConfig`, `resolveConfig`,
|
|
792
792
|
`CapabilityConfigPackage`
|
|
793
|
-
- `src/config/
|
|
794
|
-
|
|
795
|
-
|
|
793
|
+
- `src/config/config-system.ts` — `defineConfig`, `loadConfig` (reads `holocron.config.*`;
|
|
794
|
+
file discovery via [`@theholocron/datapad`](../datapad)) and `compose`, all built from
|
|
795
|
+
kyber's `createConfigSystem`; Holocron's own rules sit beside it in `config/config`,
|
|
796
|
+
`compose/{merge-*,task-name}` and `load-config/{derive-defaults,read-package-json-name}`
|
|
796
797
|
- `src/observability/logger.ts` — CLI-side `@theholocron/observability/logger` wiring
|
|
797
798
|
(`buildCliLogger`, `resolveLogLevel`)
|
|
798
799
|
- `src/loader.ts` — `PluginLoader` — dynamic-imports plugins, resolves
|
|
@@ -816,8 +817,8 @@ the local override exists to exempt.
|
|
|
816
817
|
`doctor <capability>` is listed in
|
|
817
818
|
- `src/interactive-menu/` — the interactive fallback's Holocron data: `command-registry`
|
|
818
819
|
(`COMMAND_REGISTRY`, each entry's `positionals`/`options`), `run-menu-entries`
|
|
819
|
-
and `probe-menu-entries` (menu entries built at run time), and `
|
|
820
|
-
|
|
820
|
+
and `probe-menu-entries` (menu entries built at run time), and `menu.ts`,
|
|
821
|
+
kyber's `createMenu` bound to the `holocron` bin and `HOLOCRON_` env prefix.
|
|
821
822
|
The engine itself (the picker, argv and secret env, the dry-run preview, the spawn)
|
|
822
823
|
and the prompting pieces — `promptForPositionals`, `promptForOptions` — live in
|
|
823
824
|
`@theholocron/kyber` (`/menu`, `/prompts`), which has no knowledge of commands.
|