chore: hoist mf plugin to global

[2heal1]

Summary

hoist mf plugin to global

Related Links

Checklist

• Tests updated (or not required).
• Documentation updated (or not required).

[netlify]

✅ Deploy Preview for rslib ready!

Name	Link
🔨 Latest commit	f2ef4a2
🔍 Latest deploy log	https://app.netlify.com/sites/rslib/deploys/677ce68a4922e50008f41c6d
😎 Deploy Preview	https://deploy-preview-656--rslib.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[fi3ework]

Is this change for functionality reason, or just polish code style?

[2heal1]

Is this change for functionality reason, or just polish code style?

functionality reason, we may inject variables for runtime api in the future , so the plugin need to be hoisted as global plugin .

If not , we can only affect the mf type asset , the other assets will be crashed without injecting our expected variables.

[fi3ework]

If not , we can only affect the mf type asset , the other assets will be crashed without injecting our expected variables.

So if there's a lib config which is a pure ESM or CJS output without any MF stuff, how could it bail out from runtime injecting of the plugin?

I guess something like below?

[
  { plugins: [mfPlugin]}, // MF related lib
  { plugins: [mfPlugin]}, // MF related lib
  { plugins: []},         // non-MF related lib
]

[Timeless0911]

What if there are multiple objects in lib array, global plugins will take effect for them all. How to use different options to distinguish them?

And we have supported npx rslib mf-dev --lib mf1 to choose one lib of mf format, is this feature not needed?