@appshell/config 1.0.0-alpha.90 → 1.0.0-alpha.92

package/dist/types/context.d.ts

@@ -2,7 +2,11 @@ export type AppshellContext = {
     registry?: string;
     /** Activation target as `scope/name`. */
     application?: string;
-    scopeId: string;
+    /**
+     * The addressing default, if one is configured. Optional because there is no honest
+     * value to invent when there is not — see `qualify`.
+     */
+    scopeId?: string;
     token?: string;
 };
 /**

package/dist/types/types.d.ts

@@ -51,7 +51,7 @@ export type ComparisonTarget = {
  * It used to live in the set handler, and adding `caFile` to CliConfig without touching it
  * produced a setting the cli could read and refuse to write.
  */
-export declare const CLI_SETTINGS: readonly ["registry", "application", "scopeId", "authIssuer", "clientId", "apiKey", "apiKeyHeader", "caFile"];
+export declare const CLI_SETTINGS: readonly ["registry", "application", "defaultScope", "authIssuer", "clientId", "apiKey", "apiKeyHeader", "caFile"];
 export type CliSetting = (typeof CLI_SETTINGS)[number];
 export type CliConfig = Record<string, string> & {
     apiKey: string;
@@ -63,7 +63,20 @@ export type CliConfig = Record<string, string> & {
     caFile?: string;
     registry: string;
     application: string;
-    scopeId: string;
+    /**
+     * Which namespace an unqualified name belongs to, absent anything better.
+     *
+     * Addressing only, and named for it. It was `scope-id`, which read as *the scope this
+     * account has* — identity — and it is not: the registry takes a caller's scope from the
+     * token, and this value never reaches it. Publishing takes it from the package name.
+     * So a `scope-id` here decided where names resolved while something else decided where
+     * writes landed, and the two could disagree without anything saying so.
+     *
+     * It earns its place all the same: `resolveScopeId` falls back to the account's own
+     * scope and deliberately refuses to guess when an account owns several, and this is how
+     * that is settled without passing a flag to every command.
+     */
+    defaultScope: string;
     authIssuer: string;
     clientId: string;
 };

package/dist/types/utils/config.d.ts

@@ -1,5 +1,20 @@
 import yargs from 'yargs';
 import { CliConfig } from '../types';
+/**
+ * The addressing default: which namespace an unqualified name resolves to.
+ *
+ * Named `default-scope` and not `scope-id`, because the old name described identity —
+ * *the scope this account has* — and the value has never been that. The registry takes a
+ * caller's scope from the token and publishing takes it from the package name; this
+ * reaches neither. A `scope-id` deciding where names resolved while something else decided
+ * where writes landed is how the two came to disagree without anything saying so.
+ *
+ * Stated once because the cli and the webpack plugin both need the answer, and two
+ * precedence chains for one setting is how they drift apart.
+ */
+export declare const resolveDefaultScope: (config: {
+    defaultScope?: string;
+}, env?: NodeJS.ProcessEnv) => string | undefined;
 export declare const readConfig: (configPath: string) => CliConfig;
 export declare const writeConfig: (configPath: string, config: CliConfig) => void;
 export declare const mergeConfigWithArgs: (config: CliConfig, argv: yargs.ArgumentsCamelCase<unknown>) => void;

package/dist/types/utils/index.d.ts

@@ -1,6 +1,6 @@
 export { default as blur } from './blur';
 export { compareDependencies, compareDependency, compareSharedDependencies, compareSharedModules, extractDependencies, printResults, } from './compare';
-export { mergeConfigWithArgs, readConfig, writeConfig } from './config';
+export { mergeConfigWithArgs, readConfig, resolveDefaultScope, writeConfig } from './config';
 export { default as copy } from './copy';
 export { default as dump } from './dump';
 export { default as list } from './list';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@appshell/config",
-  "version": "1.0.0-alpha.90",
+  "version": "1.0.0-alpha.92",
   "description": "Utility for producing a global appshell manifest for module federation micro-frontends",
   "main": "dist/main.js",
   "types": "dist/types/index.d.ts",
@@ -31,9 +31,9 @@
     "appshell"
   ],
   "license": "MIT",
-  "gitHead": "8029e3d70cb9a867e61e51af23a53e5f3b96191a",
+  "gitHead": "e882b41193588bb623ada8db1e4f62b07032b21d",
   "dependencies": {
-    "@appshell/runtime": "^1.0.0-alpha.90",
+    "@appshell/runtime": "^1.0.0-alpha.92",
     "yaml": "^2.8.0"
   }
 }