@theholocron/cli 5.0.0-alpha.80 → 5.0.0-alpha.82

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
@@ -21,7 +21,7 @@ Run `holocron` with no command, a parent command with no subcommand
21
21
  missing a required positional (`holocron deploy`, `holocron secret set`), and
22
22
  you get a prompt instead of a `--help` dead end:
23
23
 
24
- ```
24
+ ```console
25
25
  $ holocron
26
26
  ? What would you like to do? › dep
27
27
  ────────────────────────────────────────────────
@@ -421,7 +421,7 @@ holocron auth set github.admin ghp_xxx # setup, secrets, environments
421
421
 
422
422
  The resolution chain per capability is:
423
423
 
424
- ```
424
+ ```text
425
425
  --token flag → HOLOCRON_<FEATURE>_TOKEN env var → keyring("github.<feature>")
426
426
  ```
427
427
 
@@ -493,6 +493,31 @@ holds the orchestration + the Holocron-specific credential resolution
493
493
  (`telemetry/resolve.ts`). See the
494
494
  [telemetry guide](https://docs.theholocron.dev/holocron/telemetry/).
495
495
 
496
+ ### ESLint bundle options
497
+
498
+ Most repos need nothing here — `@theholocron/eslint-config`'s `library()`
499
+ bundle resolves with zero committed file (Bucket A: `eslint --config
500
+ <shared path>`, no per-repo `eslint.config.ts` needed). A package with a
501
+ genuine, deliberate exception — e.g. Web Crypto globals a Node-targeted
502
+ package still needs, exempted via `library()`'s own `browserPackages`
503
+ option in that package's own `eslint.config.ts` — should also declare the
504
+ same paths in `holocron.config`'s `eslint.browserPackages`:
505
+
506
+ ```ts
507
+ export default defineConfig({
508
+ eslint: {
509
+ browserPackages: ["packages/github-client/src/app-auth"],
510
+ },
511
+ });
512
+ ```
513
+
514
+ This doesn't replace the package's own `eslint.config.ts` (local/CI linting
515
+ still resolves that file directly) — it's the signal Sentinel's centralized
516
+ static-analysis check (holocron#849/#858) reads instead, since that check
517
+ never reads a PR's own committed config files. Without it, Sentinel flags a
518
+ false-positive `eslint-plugin-n` node-builtins finding on exactly the files
519
+ the local override exists to exempt.
520
+
496
521
  ## What's in here
497
522
 
498
523
  - `src/capabilities/` — the 14 capability interfaces that providers
package/dist/cli.mjs CHANGED
@@ -297,7 +297,8 @@ function resolveConfig(raw) {
297
297
  docs,
298
298
  env: raw.env,
299
299
  log: raw.log,
300
- telemetry: raw.telemetry
300
+ telemetry: raw.telemetry,
301
+ eslint: raw.eslint
301
302
  };
302
303
  }
303
304
  //#endregion