Support Global Plugin Regestration from init

[yuvalkarif]

Clear and concise description of the problem

Currently the only options to add global plugins are: registerGlobalPlugins or window.__FEDERATION__.__GLOBAL_PLUGIN__?.push.

There is no option to pass globalPlugins to init.

Suggested solution

Enable passing globalPlugins to the init runtime function, later to be supported from vite / webpack as well.
Example:

import runtimePlugin from 'custom-runtime-plugin.ts';
import globalRuntimePlugin from 'global-custom-runtime-plugin.ts';
init({
  name: '@demo/app-main',
  plugins: [runtimePlugin()],
  globalPlugins: [globalRuntimePlugin()], // <-- New
  remotes: [
    {
      name: "@demo/app2",
      entry: "http://localhost:3006/remoteEntry.js",
      alias: "app2"
    },
  ],
});

Alternative

We can also mark any plugin as global: true to be registered globally.

import { FederationRuntimePlugin } from '@module-federation/enhanced/runtime';
export default function (): FederationRuntimePlugin {
  return {
    name: 'custom-plugin-build',
    global: true, // <-- New
    beforeInit(args) {
      console.log('[build time inject] beforeInit: ', args);
      return args;
    },
    beforeLoadShare(args) {
      console.log('[build time inject] beforeLoadShare: ', args);
      return args;
    },
  };
}

Additional context

Willing to take part in the implementation :)

Validations

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

[ScriptedAlchemy]

Send a pull request. registerPlugins in core.ts

[yuvalkarif]

Great, will dive into it over the weekend

[ScriptedAlchemy]

After discussion with the team.
They do not want to make it easy to use global runtime plugins.
This is a very serious act to utilize them, and can cause catastrophic problems if they are overused.

The team would prefer deliberate friction, forcing the user to implement it somewhere else or in the pre-entry phases of the compiler, in their own code, or how i do it - i just register a blank runtime plugin where i use registerGlobalPlugin and just register it anyway as a side-effect of a normal runtime plugin.
The major concern is on-call pressure that supporting this feature will put on us at our company, they want it to be unfriendly and out of reach of most

[yuvalkarif]

I see, thanks !

[ScriptedAlchemy]

Sorry man! I Tried!

[yuvalkarif]

Sorry man! I Tried!

All good :) it was nice experimenting with the codebase, see ya in the next PR 🤞