Add an example with vue-router about hello-vue-components

[EvanBurbidge]

Yeah I'll write something up tonight as a basic example.

[angeliski]

I would like to see that too :)

[EvanBurbidge]

@angeliski have you done anything in regards to it? I'm still trying to crack it!

[angeliski]

Hi @EvanBurbidge I don't tried, but maybe you should not expose the full application.
You can segregate your packages to export the routes config and use I main entry point like a orchestation .

Or you can use a SPA manager like: https://github.com/CanopyTax/single-spa

[EvanBurbidge]

I might give that a shot. Need to keep trying this a little bit first though. Our BE wouldn't be setup to handle that.

Thanks for the tip @angeliski

[angeliski]

@EvanBurbidge Would you be able to make an example repository available for me to take a look at? Maybe I can suggest some other approach.

[EvanBurbidge]

@angeliski https://github.com/EvanBurbidge/mono-repo-tester/ there ya go, its simply build app2 as a lib and install into app1, but with lazy loaded routes in app2

[chrisvfritz]

Sorry for the delayed reply. I apparently wasn't watching this repo, so never saw notifications about issues/PRs. 😅 I think exporting an application is a different enough use case that it's beyond the scope of this project. However, feel free to keep discussing the problem here. 🙂

[EvanBurbidge]

Hey @chrisvfritz no problem! @angeliski the approach i've ended up taking is to not compile the development applications, instead now I am writing projects and maintaining an internal vue cli plugin which will add all non duplicated peer deps into the "consuming applications". I'm also leveraging Lerna hoisting in order to ensure that my repo doesn't duplicate packages across the board.

[angeliski]

Nice @EvanBurbidge ! You can share some code example how do you manager that?
I think will be really awesome see the orchestration working
Cheers