Few blockers on Module federation | working on vue 3 #1726
Unanswered
iamprobirdey
asked this question in
Q&A
Replies: 1 comment
-
|
Help wanted here. I don't know vue |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
In my case I tried with exposing few single component, which works perfect. Later I found each component has many nested component, so sharing a single component won't work.
So I shared my router, by adding the router to my host using
router.addRoute(remoteRouter)works perfectly.Host runs on
localhost:8080remote runs on
localhost:8082Problem 1:
My remote component api's should call
port:8082but they are callingport:8080and I am not sure how can i fix this.Problem 2:
Remote component has some generic files to call notification
Like
notification.tsLandingPage.vueThis Notify plugin couldn't find the module in the host.
I tried with pulling
notifyin component rather than using in generic ts file and it works.I think there is some ts config problem i couldn't find what could be.
Problem 3
My remote landingPage component has a button
<button href="message/create/" />It should somehow redirect to the page itself but since it's in my host app, but it effect my
host app urltsconfig.jsonvue.config.jsBeta Was this translation helpful? Give feedback.
All reactions