Skip to content
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

module Federation init too many remote.js #14837

Closed
zhangzippo opened this issue Nov 26, 2021 · 10 comments
Closed

module Federation init too many remote.js #14837

zhangzippo opened this issue Nov 26, 2021 · 10 comments

Comments

@zhangzippo
Copy link

webpack5

Bug report

when i see the code after build, i think something wrong with this:
image
the code from webpack_require.I
it case when init a remote container, all the container init env you use import(). when open first page. will init too many remote.js
i don't know why , thanks for telling me why

@zhangzippo
Copy link
Author

zhangzippo commented Nov 26, 2021

moduleFederationplugin don't add the sharescope to the ContainerReferencePlugin , if i do this , it can run when router only
init one remote, don't init all the remotes
image
image

@zhangzippo
Copy link
Author

waiting for a answer, thanks

@zhangzippo zhangzippo changed the title module ModuleFederation init too many remote.js module Federation init too many remote.js Nov 26, 2021
@vankop
Copy link
Member

vankop commented Nov 26, 2021

could you create a reproducible repo? it is hard to help you from this screenshots

@sokra
Copy link
Member

sokra commented Nov 26, 2021

might be related to #13819

@zhangzippo
Copy link
Author

oh yes, thanks.

@zhangzippo
Copy link
Author

might be related to #13819

but why it has't publish a version ? i see the pr not merge

@alexander-akait
Copy link
Member

alexander-akait commented Dec 1, 2021

Because no tests in PR

@zhangzippo
Copy link
Author

Because no tests in PR

oh that's a pity. could you fix the bug , you seems like the webpack5 's Developer

@webpack-bot
Copy link
Contributor

This issue had no activity for at least three months.

It's subject to automatic issue closing if there is no activity in the next 15 days.

@webpack-bot
Copy link
Contributor

Issue was closed because of inactivity.

If you think this is still a valid issue, please file a new issue with additional information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants