docs
evals
scenario-1
scenario-10
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
A helper that chooses the micro-frontend role for an Ice.js app and shapes bundle output so child apps expose a UMD library name.
role: "child" and library: "marketingApp", the generated config uses the dependency's plugin in child mode and sets the bundle output to UMD named "marketingApp". @testrole: "child" and library: ["legacyWidget", "modernWidget"], the generated config uses both library names for the UMD output so scripts can be consumed under either global. @testrole: "framework", the generated config uses the dependency's plugin in framework mode and leaves bundle output naming untouched. @testexport type MicroFrontendRole = "child" | "framework";
export interface MicroFrontendOptions {
role: MicroFrontendRole;
library?: string | string[];
}
export interface MicroFrontendConfig {
role: MicroFrontendRole;
plugins: unknown[]; // contains the configured micro-frontend plugin instance
}
export function createMicroFrontendConfig(options: MicroFrontendOptions): MicroFrontendConfig;Micro-frontend plugin used to select framework vs child role and set library-based UMD output. @satisfied-by