[Bug]: Support `import` Property in `shared` Configuration (Like Webpack Module Federation)

[ZiuChen]

Describe the bug

Hi everyone,

I’m using @module-federation/vite and I noticed that the shared configuration does not currently support the import property, like what’s described in the official module-federation docs.
This means it’s not possible to specify a custom import path for a shared module (for example, a local build or an aliased package).

Is this feature planned or being discussed?
It would be really helpful for advanced use cases, and it seems to already be supported for the exposes section.

If there’s a workaround or if anyone is interested in collaborating to implement this, please let me know!

Thanks for your great work on this project!

Version

v1.4.0

Reproduction

https://github.com/module-federation/module-federation-examples/blob/d7909ea7e29e1da671e8703705020abdca647d7e/shared-context/app1/webpack.config.js

Relevant log output

Validations

• Read the docs.
• Read the common issues list.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• The provided reproduction is a minimal reproducible example of the bug.