New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Name of remote module required to be remoteEntry.mjs #10206
Comments
Hey 😄 Are you also using our |
Hi, i have a mixed setup. Part of my remote modules are located within my nx workspace and are using |
Can we also have this fixed for the manifest files..? i.e. using using the |
How did you manage to configure Nx monorepo to use module which is now build with withModuleFederation? I'm trying to do it 2 days without success. All examples are just using apps from monorepo itself or it's configured with ModuleFederationPlugin without nx tooling. I'm always getting error like: remoteEntry.js from "external" repo app is loaded but this is everything. |
This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context. |
Hi, i'm integrating your module federation features for a projct and found out that you required the name of remote modules for be
remoteEntry.mjs
here. This is a issue since i have to integrate remote modules which are named differently. Wouldn't it be a better approach to check ifremoteUrl
already includes the filename and only addremoteEntry.mjs
as fallback?The text was updated successfully, but these errors were encountered: