Support consume manifest

[2heal1]

Clear and concise description of the problem

Now module federation just support consume url , and we can not get more info from url .

This prevents us from doing some performance optimization and function expansion, such as prefetch, type hints and so on .

If we can get more info like data assets, we can do more features .

Suggested solution

We can support consume manifest url . The manifest can recored data assets/version/type files . And we can load manifest to get these infos , and then do some features as we need .

Basic Usage

• generate manifest

set options.manifest as true to enable generate manifest

import { ModuleFederationPlugin } from '@moduel-federation/universe';

new ModuleFederationPlugin({
  manifest: true
});

• consume manifest

set remote value url as manifest url :

import { ModuleFederationPlugin } from '@moduel-federation/universe';

new ModuleFederationPlugin({
    remotes: {
      remote1: 'webpack_provider@http://localhost:3009/mf-manifest.json',
      'manifest-provider':
        'rspack_manifest_provider@http://localhost:3011/mf-manifest.json',
      'js-entry-provider':
        'rspack_js_entry_provider@http://localhost:3012/remoteEntry.js',
    },
});

Detail Design

The manifest has mainly four parts : metaData、remotes、exposes、shared .

• metaData: record provider self info like publicPath、remoteEntry and so on
• exposes: record expose file asstes 、requires(shared) and so on
• shared: record shared assets、usedIn(exposes) and so on
• remotes: record remote entry 、uesdIn and so on

What can we do with this data?

1. Optimize performance

We can preload the remote assets though manifest.expose/shared.assets in these scens:

• loadRemote: When users call loadRemote or just import remote , we can auto preload assets in runtime hooks
• Idle time: Users can manually call preloadRemote in idle time.
• framework router: Now modern framework almost have loaders which can help to preload current route mf module assets .

2. Analyze reference relationships between modules

Because manifest has remotes and exposes fields , so we can easily know the relationship , and we can use it to draw a complete reference diagram.

3. Cooperate with the deployment platform for data distribution to improve performance

If users have PageServer , they can use manifest to deliver complete dependencies , and with this it can also make version/tag for MF modules.

Alternative

No response

Additional context

No response

Validations

• Read the Contributing Guidelines.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.