#mf-manifest.json Field Reference

mf-manifest.json is generated when manifest is enabled. It is a runtime-oriented manifest distilled from mf-stats.json, keeping a stable, consumer-friendly shape.

#Top-level

#Field Differences vs mf-stats.json

#metaData (Both Files)

metaData describes how this build is consumed at runtime and the build context. Both mf-stats.json and mf-manifest.json include it.

#StatsMetaData

StatsMetaData has two mutually exclusive shapes:

• Function form: getPublicPath: string
• String form: publicPath: string (optional ssrPublicPath: string)

Shared fields:

| Field | Type | Required | Description | | ------------------- | ---------------- | -------- | ------------------------------------- | --- | | name | string | Yes | Current remote/host name | | globalName | string | Yes | Global name for the remoteEntry | | buildInfo | StatsBuildInfo | Yes | Build information | | remoteEntry | ResourceInfo | Yes | Remote entry resource | | ssrRemoteEntry | ResourceInfo | No | SSR remote entry (if any) | | prefetchInterface | boolean | No | Whether prefetch interface is enabled | | prefetchEntry | ResourceInfo | No | Prefetch resource (if any) | | types | MetaDataTypes | No | Types bundle info (if any) | | type | string | Yes | APP | NPM | | pluginVersion | string | No | MF Plugin version |

#ResourceInfo

#StatsBuildInfo

#MetaDataTypes

#assets (Both Files)

StatsAssets describes sync/async assets for a shared or exposed module. Both files use it.

#StatsAssets

#StatsAssetsInfo

#shared (ManifestShared vs StatsShared)

mf-manifest.json keeps only the essential shared fields needed at runtime.

#remotes (ManifestRemote vs StatsRemote)

mf-manifest.json keeps the minimal set needed to locate and load a remote.

#exposes (ManifestExpose vs StatsExpose)

mf-manifest.json exposes only runtime consumer fields.