@appshell/runtime 1.0.0-alpha.63 → 1.0.0-alpha.65

package/dist/types/index.d.ts

@@ -3,4 +3,4 @@ export { ANONYMOUS, getIdentity } from './identity';
 export type { Identity } from './identity';
 export { hasVars, readVars, resetVars, setVars } from './store';
 export type { Vars } from './types';
-export type { AppshellIndex, AppshellRemote, Metadata } from './wire';
+export type { AppshellIndex, AppshellRemote, Metadata, ModuleFederationLoader, RemoteLoader, } from './wire';

package/dist/types/wire.d.ts

@@ -12,14 +12,46 @@
  */
 /** Arbitrary, application-defined description of a remote. Appshell never reads it. */
 export type Metadata = Record<string, unknown>;
+/**
+ * How a host loads a remote, named as one kind among possible kinds.
+ *
+ * scope, module and shareScope are Module Federation's vocabulary, and they used to sit
+ * at the top level of a remote where nothing said so — which is what would have made a
+ * second framework awkward, not the words themselves. Nested under a kind they are
+ * exactly correct, and something like single-spa slots beside them without reinterpreting
+ * anything already published.
+ *
+ * apiVersion follows the house style set by appshell.app.yaml, and the group is appshell's
+ * because appshell owns this schema: it decides which fields it stores, even though the
+ * fields describe federation concepts. If federation ever needs a different recipe that is
+ * a v2, and manifests published under v1 keep meaning what they meant — which matters,
+ * because they are immutable and hashed.
+ */
+export type ModuleFederationLoader = {
+    apiVersion: 'federation.appshell.org/v1';
+    kind: 'ModuleFederation';
+    scope: string;
+    module: string;
+    shareScope?: string;
+    /** The entry file the build emits, conventionally remoteEntry.js. */
+    filename: string;
+    /**
+     * What built this, recorded as a fact rather than a constraint.
+     *
+     * Deliberately not a version range. A range is a claim about the environment, and a
+     * package cannot make it: it knows what built it and not what will load it, and the
+     * host is what registers the remote. Freezing one into an immutable artifact is the
+     * same mistake as freezing its origin.
+     */
+    builtWith?: string;
+};
+export type RemoteLoader = ModuleFederationLoader;
 /** A remote the registry has already resolved, so the browser needs no manifest fetch. */
 export type AppshellRemote<TMetadata = Metadata> = {
     id: string;
     manifestUrl: string;
     remoteEntryUrl: string;
-    scope: string;
-    module: string;
-    shareScope?: string;
+    loader: RemoteLoader;
     metadata: TMetadata;
 };
 /** Remote key to manifest url. */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@appshell/runtime",
-  "version": "1.0.0-alpha.63",
+  "version": "1.0.0-alpha.65",
   "description": "The shared singleton that delivers a package's runtime configuration to it",
   "main": "dist/main.js",
   "types": "dist/types/index.d.ts",
@@ -49,5 +49,5 @@
     "appshell"
   ],
   "license": "MIT",
-  "gitHead": "385f10aa2c4074e3fec2e630d91503b5acbb3c9e"
+  "gitHead": "1ce899539b6ab3063880835140a65e590c2dad21"
 }