Documentation inconsistency between @module-federation/enhanced/runtime and @module-federation/runtime

[540792740]

I noticed an inconsistency in the runtime documentation and examples.

The documentation mentions using: @module-federation/enhanced/runtime
Link(https://module-federation.io/guide/runtime/index.html)

However, the Vite example appears to use: @module-federation/runtime
Link(https://github.com/module-federation/vite/blob/main/examples/vite-runtime-register/vite-host/package.json)

This makes it unclear which package is currently recommended for runtime APIs in Vite-based projects.

Questions

• Which package should be considered the recommended runtime package today?
• What is the relationship between:
  • @module-federation/runtime
  • @module-federation/enhanced/runtime
• Are there feature or compatibility differences between them?
• Should Vite users prefer one over the other?

Suggestion
It would help to clarify this in the documentation by:

• explicitly documenting the intended usage of each package
• aligning examples with the recommended approach
• adding migration guidance if one package supersedes the other

Environment

• Vite
• React
• Module Federation runtime APIs

[vincere-mori]

At the current package layout these are effectively the same runtime API, just reached through different packages.

The chain is:

@module-federation/enhanced/runtime
  -> @module-federation/runtime-tools/runtime
  -> @module-federation/runtime

So @module-federation/runtime is the standalone runtime package, and @module-federation/enhanced/runtime is a convenience re-export from the higher-level enhanced package.

For a Vite-only project, I would import from @module-federation/runtime directly if you are not already depending on @module-federation/enhanced. It is the smaller and clearer dependency.

If your setup already uses @module-federation/enhanced, importing from @module-federation/enhanced/runtime is also fine and keeps the runtime API version tied to the enhanced package version.

So I don't think one supersedes the other; the docs/examples are mixing the wrapper import and the underlying package. A short note in the docs saying that enhanced/runtime re-exports the standalone runtime would remove most of the confusion.