Custom Library Naming for Micro Frontends

Configure a child micro-frontend build so it exposes an explicit library label (or labels) and publishes that label to the host discovery global. The label comes from the MICRO_LIB_LABELS environment variable (comma-separated values indicate multiple aliases) and falls back to the package name when unset.

Capabilities

Honors explicit label

• When MICRO_LIB_LABELS is set to billingShell, the child bundle exposes that label as the library name and assigns the same value to window.ICESTARK.library after the entry runs. @test

Supports multiple aliases

• When MICRO_LIB_LABELS contains comma-separated values billingShell,BILLING_SHELL, the build configuration uses them as an ordered array for the library name and window.ICESTARK.library reflects the same array. @test

Falls back to package name

• With no explicit label, the configuration relies on the package metadata name to pick the library label and publishes that label to both the bundle export and window.ICESTARK.library. @test

Emits UMD child bundle

• The child micro-frontend build targets UMD (libraryTarget: 'umd') with the chosen library name so host frameworks can mount it. @test

Implementation

@generates

API

import type { UserConfig } from '@ice/app';

declare const config: UserConfig;
export default config;

Dependencies { .dependencies }

@ice/plugin-icestark { .dependency }

Provides micro-frontend build plugin support for child bundles, custom library names, and host global wiring.