Manifest Field Reference

mf-manifest.json é generated quando manifest é habilitado. It é uma runtime-oriented manifest distilled de mf-stats.json, keeping uma stable, consumer-friendly shape.

Top-level

Field	Tipo	Obrigatório	mf-stats.json	Description
`id`	`string`	Yes	Yes	Unique build identifier
`name`	`string`	Yes	Yes	Federation name
`metaData`	`StatsMetaData`	Yes	Yes	Build e remote entry info
`shared`	`ManifestShared[]`	Yes	Yes (fuller)	Shared list (trimmed fields)
`remotes`	`ManifestRemote[]`	Yes	Yes (fuller)	Remotes list (trimmed fields)
`exposes`	`ManifestExpose[]`	Yes	Yes (fuller)	Expõe list (trimmed fields)

disableAssetsAnalyze impact

Quando disableAssetsAnalyze: true é definir em manifest, mf-manifest.json vai omit shared e exposes, e remotes vai omit assets.

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)
`types`	`MetaDataTypes`	No	Types bundle info (if any)
`type`	`string`	Yes	APP, NPM
`pluginVersion`	`string`	No	MF Plugin version

ResourceInfo

Field	Type	Required	Description
`path`	`string`	Yes	Relative path in build output
`name`	`string`	Yes	File name
`type`	`RemoteEntryType`	Yes	Remote entry format (`var/umd/system/...`)

StatsBuildInfo

Field	Type	Required	Description
`buildVersion`	`string`	Yes	Build version
`buildName`	`string`	Yes	Build name
`target`	`string[]`	No	Build targets
`plugins`	`string[]`	No	Tree-shaking plugins
`excludePlugins`	`string[]`	No	Tree-shaking exclude plugins

MetaDataTypes

Field	Type	Required	Description
`path`	`string`	Yes	Output path
`name`	`string`	Yes	File name (required for legacy types, will be deprecated)
`api`	`string`	Yes	API entry
`zip`	`string`	Yes	Zip path

assets (Both Files)

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

StatsAssets

Field	Type	Required	Description
`js`	`StatsAssetsInfo`	Yes	JavaScript assets
`css`	`StatsAssetsInfo`	Yes	CSS assets

StatsAssetsInfo

Field	Type	Required	Description
`sync`	`string[]`	Yes	Initial assets
`async`	`string[]`	Yes	Async assets

shared (ManifestShared vs StatsShared)

mf-manifest.json keeps apenas o essential shared fields needed em runtime.

Field	mf-manifest.json	mf-stats.json
`id`	Yes	Yes
`name`	Yes	Yes
`version`	Yes	Yes
`singleton`	Yes	Yes
`requiredVersion`	Yes	Yes
`hash`	Yes	Yes
`assets`	Yes	Yes
`deps`	No	Yes
`usedIn`	No	Yes
`usedExports`	No	Yes
`fallback`	Opcional	Yes
`fallbackName`	Opcional	Yes
`fallbackType`	Opcional	Yes

remotes (ManifestRemote vs StatsRemote)

mf-manifest.json keeps o minimal definir needed para locate e carregue uma remote.

Field	mf-manifest.json	mf-stats.json
`moduleName`	Yes	Yes
`federationContainerName`	Yes	Yes
`alias`	Yes	Yes
`consumingFederationContainerName`	No	Yes
`usedIn`	No	Yes
`entry` / `version` (one de)	Yes	Yes

exposes (ManifestExpose vs StatsExpose)

mf-manifest.json exposes apenas runtime consumer fields.

Field	mf-manifest.json	mf-stats.json
`id`	Yes	Yes
`name`	Yes	Yes
`path`	Yes	Yes
`assets`	Yes	Yes
`file`	No	Yes
`requires`	No	Yes

#Manifest Field Reference

#Top-level

#Field Differences vs mf-stats.json

#metaData (Both Files)

#StatsMetaData

#ResourceInfo

#StatsBuildInfo

#MetaDataTypes

#assets (Both Files)

#StatsAssets

#StatsAssetsInfo

#shared (ManifestShared vs StatsShared)

#remotes (ManifestRemote vs StatsRemote)

#exposes (ManifestExpose vs StatsExpose)