generate mf-manifest.json when publicPath is set to 'auto'

[Scar-face]

Amazing updated with Module Federation 2.0!!!
I have recently implemented the first version for my code and upgraded to the new version. An observation when working with producer application was that the mf-manifest.json is not getting generated when publicPath is 'auto', for other values the file gets generated.

When an empty value is provided, the container requests the file relative to its path.
Can you please help me understand how the webpack configuration can be configured to generate the mf-manifest.json file for higher environments and makes call to the right host?

Below is the module federation configuration that I am using along with React 18 and @module-federation/enhanced: 0.1.11.

output: {
  publicPath: 'auto', //no mf-manifest.json is generated.  with '', mf-manifest.json gets generated.
},
plugins: [
  new ModuleFederationPlugin({
	name: 'remote',
	exposes: {
	  './Button': './src/micro-frontend/Button',
	},
	shared: {
	  react: {
		singleton: true,
		requiredVersion: require('react/package.json').version,
		eager: true,
	  },
	  'react-dom': {
		singleton: true,
		requiredVersion: require('react-dom/package.json').version,
		eager: true,
	  },
	},
  }),
],

[ScriptedAlchemy]

This has been implemented now