@appshell/config 1.0.0-alpha.60 → 1.0.0-alpha.61

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.
@@ -11,6 +11,7 @@ export { default as outdated } from './outdated';
11
11
  export { activate, openOverlay, publish } from './publish';
12
12
  export type { OpenedOverlay, OverlayRemotePatch, PublishOptions, PublishResult } from './publish';
13
13
  export { default as sync } from './sync';
14
+ export { caFile, httpsAgent } from './tls';
14
15
  export type { AppshellComposition, AppshellConfig, AppshellConfigRemote, AppshellIndex, AppshellManifest, AppshellRemote, AppshellTemplate, AppshellTokenUsage, ComparisonResult, ComparisonResults, ComparisonTarget, Metadata, ModuleFederationPluginOptions, PackageSpec, ResolvedRemote, Schema, SharedConfig, SharedModuleSpec, SharedObject, } from './types';
15
16
  export * as utils from './utils';
16
17
  export * as validators from './validators';
@@ -0,0 +1,23 @@
1
+ import https from 'https';
2
+ /**
3
+ * An extra CA bundle to trust, from `ca-file` in the cli config or `APPSHELL_CA_FILE`.
4
+ *
5
+ * A registry behind a private CA — a corporate root, a TLS-inspecting proxy, or a local
6
+ * cluster using mkcert — fails with "unable to verify the first certificate", which says
7
+ * nothing about which host or what to do. Node can be told through `NODE_EXTRA_CA_CERTS`
8
+ * or `--use-system-ca`, but both are environment variables a user has to remember in
9
+ * every new terminal, and neither travels with the registry they apply to.
10
+ *
11
+ * npm draws the same conclusion with `cafile` in .npmrc: trust is configuration of the
12
+ * registry you talk to, not of the shell you happen to be in.
13
+ */
14
+ export declare const caFile: () => string | undefined;
15
+ /**
16
+ * The agent to use for registry and issuer requests, or undefined when no CA is
17
+ * configured and Node's defaults apply.
18
+ *
19
+ * A configured file that does not exist throws rather than being skipped: falling back
20
+ * silently would reproduce the original certificate error, having been told exactly how
21
+ * to avoid it.
22
+ */
23
+ export declare const httpsAgent: () => https.Agent | undefined;
@@ -47,6 +47,12 @@ export type ComparisonTarget = {
47
47
  };
48
48
  export type CliConfig = Record<string, string> & {
49
49
  apiKey: string;
50
+ /**
51
+ * PEM bundle to trust in addition to Node's built-ins, for a registry behind a private
52
+ * CA. Optional, and absent from `config init` output: an empty path is not a default
53
+ * worth writing, and its absence means "use Node's defaults".
54
+ */
55
+ caFile?: string;
50
56
  registry: string;
51
57
  application: string;
52
58
  scopeId: string;
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@appshell/config",
3
- "version": "1.0.0-alpha.60",
3
+ "version": "1.0.0-alpha.61",
4
4
  "description": "Utility for producing a global appshell manifest for module federation micro-frontends",
5
5
  "main": "dist/main.js",
6
6
  "types": "dist/types/index.d.ts",
@@ -31,9 +31,9 @@
31
31
  "appshell"
32
32
  ],
33
33
  "license": "MIT",
34
- "gitHead": "110a91fc8a3b913ef5f65511d7edbecef26bc1c9",
34
+ "gitHead": "f5b20c95dabe1a721f2560dc4af4c4e2dc44ddd4",
35
35
  "dependencies": {
36
- "@appshell/runtime": "^1.0.0-alpha.60",
36
+ "@appshell/runtime": "^1.0.0-alpha.61",
37
37
  "yaml": "^2.8.0"
38
38
  }
39
39
  }