@appshell/config 1.0.0-alpha.71 → 1.0.0-alpha.73

package/dist/types/generate.manifest.d.ts

@@ -17,7 +17,6 @@ export declare const manifestFrom: <TMetadata extends Record<string, unknown>>(t
     components: Record<string, import("./types").PublishedRemote<TMetadata>>;
     remotes?: string[];
     shared?: import("./types").SharedContract;
-    bundle?: import("./types").BundleDigest;
     tokens?: Record<string, import("./types").AppshellTokenUsage>;
     overrides?: import("./types").AppshellOverrides;
 };
@@ -31,7 +30,6 @@ declare const _default: <TMetadata extends Record<string, unknown>>(templatePath
     components: Record<string, import("./types").PublishedRemote<TMetadata>>;
     remotes?: string[];
     shared?: import("./types").SharedContract;
-    bundle?: import("./types").BundleDigest;
     tokens?: Record<string, import("./types").AppshellTokenUsage>;
     overrides?: import("./types").AppshellOverrides;
 } | null>;

package/dist/types/index.d.ts

@@ -7,6 +7,7 @@ export type { AppshellContext } from './context';
 export { clearCredential, credentialsPath, resolveToken, saveCredential } from './credentials';
 export type { Credential } from './credentials';
 export { default as generateManifest, manifestFrom } from './generate.manifest';
+export { loaderOf } from './loader';
 export { default as outdated } from './outdated';
 export { activate, openOverlay, publish } from './publish';
 export type { OpenedOverlay, OverlayRemotePatch, PublishOptions, PublishResult } from './publish';

package/dist/types/loader.d.ts

@@ -0,0 +1,18 @@
+import { ModuleFederationLoader } from './types';
+/**
+ * How to load one component, derived from the Module Federation config that emits it.
+ *
+ * One definition, used twice: the manifest a publish stores, and the patch an overlay
+ * sends. Those describe the same thing from either side of a publish, and two copies of
+ * the derivation would disagree the moment one of them changed — the drift being that an
+ * overlay addresses a dev server's bundle by a container name the build no longer uses,
+ * which surfaces as module federation failing to find a container rather than as anything
+ * naming the cause.
+ *
+ * The federation fields sit under a kind rather than at the top level, so they read as one
+ * framework's vocabulary rather than as something generic.
+ */
+export declare const loaderOf: (module: {
+    shareScope?: string;
+    filename?: string;
+}, federationKey: string) => ModuleFederationLoader;

package/dist/types/mappers/appshell.config.d.ts

@@ -4,7 +4,6 @@ export declare const toAppshellManifest: <TMetadata extends Record<string, unkno
     components: Record<string, PublishedRemote<TMetadata>>;
     remotes?: string[];
     shared?: SharedContract;
-    bundle?: import("../types").BundleDigest;
     tokens?: Record<string, import("../types").AppshellTokenUsage>;
     overrides?: import("../types").AppshellOverrides;
 };

package/dist/types/publish.d.ts

@@ -1,4 +1,4 @@
-import { AppshellManifest, Metadata } from './types';
+import { AppshellManifest, Metadata, ModuleFederationLoader } from './types';
 export type PublishOptions = {
     registry: string;
     token?: string;
@@ -28,10 +28,22 @@ export declare const publish: ({ registry, token, name, version, manifest, visib
  * @param application `scope/name`
  */
 export declare const activate: (registry: string, application: string, packageId: string, token?: string) => Promise<void>;
-/** What an overlay redirects a single remote to. */
+/** What an overlay redirects a single remote to, or introduces one as. */
 export type OverlayRemotePatch = {
     remoteEntryUrl: string;
     manifestUrl?: string;
+    /**
+     * How to load this build's copy, from the Module Federation config that emits it.
+     *
+     * Sent because the loader describes the code being loaded, and an overlay points at
+     * this build rather than the published one. Without it a redirect addresses a dev
+     * server's bundle by whatever container name the last publish happened to have, so
+     * renaming the container locally resolves to a container the browser cannot find.
+     *
+     * It is also what lets an overlay introduce a component that is not published yet: a
+     * redirect inherits the published loader, an addition has no published anything.
+     */
+    loader?: ModuleFederationLoader;
     /**
      * The remote's `metadata` as this build declares it.
      *

package/dist/types/types.d.ts

@@ -120,11 +120,6 @@ export type AppshellConfig<TMetadata = Metadata> = {
 };
 export type AppshellTemplate<TMetadata = Metadata> = {
     name?: string;
-    /**
-     * Digest of everything the build emitted, computed during the compilation. On the
-     * template rather than in the yaml because only the build knows it.
-     */
-    bundle?: BundleDigest;
     /** Carried from the yaml for publish to read; never mapped into the manifest. */
     visibility?: 'public' | 'private';
     components?: Record<string, AppshellConfigRemote<TMetadata>>;
@@ -169,24 +164,6 @@ export type AppshellTokenUsage = {
     required: string[];
     optional: string[];
 };
-/**
- * A digest of the bytes a package emitted, so its identity covers its code.
- *
- * Without it a manifest describes a bundle it cannot vouch for. The addresses a package
- * asks the registry for live in its source, not in anything it declares — so an edit that
- * changed which remotes it loads left the manifest byte-identical, and republishing the
- * changed build was a no-op rather than a version conflict. Two builds that differ
- * anywhere are now different packages.
- *
- * Over every emitted asset rather than the entry alone. The entry does change whenever a
- * chunk does — but only where chunk filenames carry a content hash, which is a convention
- * a project may not follow and nothing here can enforce.
- */
-export type BundleDigest = {
-    algorithm: 'sha384';
-    /** Base64, over each asset's name and bytes in sorted order. */
-    digest: string;
-};
 /** A shared-dependency contract, named as one framework's model among possible models. */
 export type SharedContract = {
     apiVersion: 'federation.appshell.org/v1';
@@ -209,8 +186,6 @@ export type AppshellManifest<TMetadata = Metadata> = {
      * type-generation flags sat inside the package digest.
      */
     shared?: SharedContract;
-    /** What this package's code hashes to; absent when built outside a compilation. */
-    bundle?: BundleDigest;
     vars: Record<string, Record<string, string | number | undefined>>;
     /** Keyed by federation scope, so a merged manifest still says which package needs what. */
     tokens?: Record<string, AppshellTokenUsage>;
@@ -262,6 +237,16 @@ export type AppshellComposition<TMetadata = Metadata> = {
     overlay?: {
         id: string;
         remotes: string[];
+        /**
+         * Those of `remotes` the overlay introduced rather than redirected — components the
+         * application does not publish, running for this developer and nobody else.
+         *
+         * Separate from `remotes` because the two are not the same claim. A redirected
+         * component exists for everyone and this browser runs a different copy of it; an
+         * added one does not exist outside this overlay at all, so a feature built on top of
+         * one works here and is absent everywhere else.
+         */
+        added?: string[];
         shellFlavor: 'prod' | 'dev';
         theme?: string;
     };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@appshell/config",
-  "version": "1.0.0-alpha.71",
+  "version": "1.0.0-alpha.73",
   "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": "2605aafa8f54460c6c05c175f657ef0a830570ab",
+  "gitHead": "00740825a81e453566a3333d8253afc6a9744310",
   "dependencies": {
-    "@appshell/runtime": "^1.0.0-alpha.71",
+    "@appshell/runtime": "^1.0.0-alpha.73",
     "yaml": "^2.8.0"
   }
 }