-
Notifications
You must be signed in to change notification settings - Fork 399
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
Fire and wait pattern using Observables with HttpClient doesn't work when mfes' are being loaded using webpack #1921
Comments
None of the core team have worked on a MFE app, so this exploration is really interesting. Thank you! And thank you for the awesome effort that you went into for the repro!. I won't have a moment to crack open the repro right now, but I do have a thought on where this could be going wrong...
and
I suspect that this would not work if there are different versions of Have you followed this guide? If the guide is lacking anything then any contributions would be super welcome! |
@markwhitfeld yes we have checked the guide that you have mentioned.
We have marked It doesn't work for us. Please let me know if there are any gaps in our understanding. |
@markwhitfeld we'll try adding |
@markwhitfeld thanks for the suggestion. Can you please share the document repository link, so that I can update the guide. But I do feel this need a correction. Other popular store library do work without this configuration in |
We will look into this issue. |
Yes, I think that we need to find a better way to detect the instance of an
observable, as I think that this is the blocker to seeing this work like
other libraries.
Here is the markdown file in the repository for that documentation page:
https://github.com/ngxs/store/blob/release/docs/recipes/module-federation.md
An update would be greatly appreciated. Thank you!
…On Thu, 29 Sept 2022 at 15:46, Swarnadeep Saha ***@***.***> wrote:
@markwhitfeld <https://github.com/markwhitfeld> the for the suggestion.
it works with "rxjs": { singleton: true, requiredVersion: 'auto' }.
Here without singleton: true it is not working, so this configuration is
important.
Can you please share the document repository link, so that I can update
the guide.
But I do feel this need a correction. Other popular store library do work
without this configuration in webpack.config.js
—
Reply to this email directly, view it on GitHub
<#1921 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAO3U2LR3JWX3UVQGKWEODDWAWMRZANCNFSM6AAAAAAQYVD6PA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Thanks! |
@markwhitfeld do we need to update https://github.com/ngxs/store/blob/release/docs/recipes/module-federation.md as the fix will be available in |
This has been fixed as part of the v3.7.6 release. |
@arturovt issue is resolved. Really thankful for all the efforts. |
I'm submitting a...
Current behavior
When MFEs are loaded using webpack, It's not working when the handler is returned to the asynchronous work from the @action method which involved backend HTTP call using angular's HTTP client.
GIF - not working when mfe is loaded using webpack
Details of the issue here
Expected behavior
Expecting this should work even when loaded/build using webpack, as it used to work earlier with
GIF - expected behavior when mfe is loaded using webpack
Minimal reproduction of the problem with instructions
Github repo
npm start
from package.jsonApp1
counter is not working and there are no backend HTTP calls when you click the button.Host
andApp2
it's working fine.GIF - not working when mfe is loaded using webpack
App2
individually by runningnpm start:app1
from package.json, it works!GIF - App1 works fine when loaded/run individually without using webpack
What is the motivation/use case for changing the behavior?
PNG - micro front end architecture using webpack module federation
In micro frontend architecture there could be mutiple UI project with it's own store instance, which can run, build & deploy individually and also can be loaded and used in the container shell or from any other ui applications.
Environment
The text was updated successfully, but these errors were encountered: