fix: resolve dts-related files relative to remote manifest file

[semekh]

I'm sending this PR as a draft to see if you see this approach fit. I will add/fix tests if you are ok with the general idea.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 2659ef4

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[netlify]

✅ Deploy Preview for module-federation-docs ready!

Name	Link
🔨 Latest commit	2659ef4
🔍 Latest deploy log	https://app.netlify.com/sites/module-federation-docs/deploys/663f19bf0ca1780008f81982
😎 Deploy Preview	https://deploy-preview-2477--module-federation-docs.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.

[ScriptedAlchemy]

Can you describe the use case or issue?

[semekh]

@ScriptedAlchemy We have a MFE architecture. And we have the following requirements for our builds:

1. We'd like to build each MFE in an isolated environment so it can not access other modules in the deployment environment during build.
2. We'd like to use the same build for multiple environments using different domains, so we build without setting the hostname in any URLs.
3. We'd like to mix modules on dev machine: I'd like to run yarn dev, consume types from multiple remotes on a deployed build, and my own dev machine. We'd like dts to just work.

Up until dts, everything was automatically handled using relative URLs, so we could just deploy on any domain/path and everything would work. But with dts, this was not the case, since the dev machine has no idea which host to look for mf-types on, since we don't set a hostname during build phase.

We're currently handling the situation through using getPublicPath function and it's working. But I assume this usecase is a common one, and also it's in line with module federation working with relative URLs everywhere else.

[ScriptedAlchemy]

Try public path auto. I just introduced its support back to MF manifests. Will auto mode work?

[ScriptedAlchemy]

@semekh does auto meet your needs?

[semekh]

It looks like it does. Didn't have the chance to test it out yet though.

[ScriptedAlchemy]

Okay @semekh do you want to close/reopen if it doesnt do whats needed?

[semekh]

Sure. Thanks.