-
Notifications
You must be signed in to change notification settings - Fork 25
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
v1.0.0: Error with Nuxt as host app #73
Comments
The entry insertion code may not take into account the SSR application. I will fix it later. |
@David-Sellen thanks for your feedback. Can I ask you to add a Nuxt example please? You can add it next to the other ones. Appreciate |
SSR requires me to complete manifest.json in advance, which is originally on the roadmap, This will take some time, I will finish it this week WARN [ Federation Runtime ]: [ Federation Runtime ]: Failed to get manifestJson for @namespace/viteViteRemote. The manifest URL is http://localhost:5176/.vite/manifest.json. Please ensure that the manifestUrl is accessible.
Error message:
Error: [ Federation Runtime ]: http://localhost:5176/.vite/manifest.json is not a federation manifest
Error message:
Error: [ Federation Runtime ]: http://localhost:5176/.vite/manifest.json is not a federation manifest |
The demo can be created, I will fix it this week |
That sounds great @zhangHongEn ! I created a small Nuxt example here: https://github.com/David-Sellen/vite/tree/73-error-with-nuxt-as-host-app @gioboa |
Thanks @David-Sellen 👏 |
Closed by #86 |
Sorry, nuxt is not yet completed. This issue needs to be reopened
…---- Replied Message ----
| From | Giorgio ***@***.***> |
| Date | 09/15/2024 19:47 |
| To | module-federation/vite ***@***.***> |
| Cc | zhn ***@***.***>,
Mention ***@***.***> |
| Subject | Re: [module-federation/vite] v1.0.0: Error with Nuxt as host app (Issue #73) |
Closed by #86
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Also tried to get this working, but still not working. https://nuxt.com/docs/guide/going-further/experimental-features#asyncentry |
nuxt should wait for rolldown support |
Hey @David-Sellen , thanks for opening this issue, and for the examples. |
@gioboa @zhangHongEn why do we need rolldown for this? let's keep the issue open, as nuxt support will pave the way for many others like Analog, solidstart as they also use nitro. |
yesterday, I spent 5 hours trying to get that working and would love to see that happen, just for the sake of those hours 😅 |
So do you have any ideas how to fix it at this moment? Nuxt support is really must have:) |
There are still some unresolved issues: nuxt/nuxt#28911. The most important thing is that I really don’t have time recently. I will continue working on it when I have some free time, but it won’t be very soon. |
Hi there!
I have a Nuxt application acting as host and to load remote client side Vue apps. Currently we're using @originjs/vite-plugin-federation which works OK but we would like to migrate to this library instead for other reasons.
I'm trying out @module-federation/[email protected] and it works well when i test it on my simple Vue SPA host but not when I'm trying to replace the OriginJS plugin in our Nuxt host application.
I get the following error in the browser and when I check the network traffic it does not load the RemoteEntyr.js.
The Vite settings in the Nuxt.config
Might there be something in this library that does not support this approach or do you guys have something that I can try out to make it work?
The text was updated successfully, but these errors were encountered: