Using both vike-react and vike-vue in the same project

[brillout]

In principle, and as stated in the documentation, it's possible to use both React and Vue (or any other UI framework) for the same project.

This should already work today with a custom React/Vue integration. (Although note that, until this issue is fixed, you'll need to use Server Routing if you plan to have both +Page.jsx and +Page.vue.)

There are currently two limitations for using vike-react and vike-vue in the same app:

• When navigating between React and Vue pages, Client Routing should be disabled while falling back to Server Routing.
• Vike.Config is corrupt (the declaration merging of vike-react and vike-vue are conflicting). Instead the user needs to stich the types himself.

If you want to use both vike-react and vike-vue write a comment down below explaining why.

[vitalybaev]

Well, I would say that for me it's not a truly necessary feature, but a nice-to-have for the following reasons/use cases:

• Long term migration. I've done some of such long going framework migration and so far the only way to achieve it is to have two separate projects and use top-level router to switch route by route from the old framework to the new one. If we had all of them in one project, we could have changed only route group between and that's it. We also could have shared styles, logic (especially with modern framework-agnostic STM) or other resources. Yes, monorepos can tackle this problem but involve additional complexity.
• Different projects -- Though it's not and ideal scenario, but sometimes, especially in relatively big companies, different projects can be powered with different technologies and maintained by different separated teams. For example, main product on React and blog on Vue.

Regarding routing limitations -- I don't know so far how it's solved in Vike, but it can be solved the same way router knows that a particular link is external (and should be handled by regular browser navigation) or can be handled by the client side router.

And just to clarify, I wouldn't have opened this issue, if the documentation didn't claim it is possible.
For me, personally, it could have been an outstanding, but not that important feature and you should weight complexity of solving this issue. I really love Vike and think you should pay attention on most important things right now.

[brillout]

I wouldn't have opened this issue, if the documentation didn't claim it is possible.

Makes sense, I just removed it.

you should pay attention on most important things right now.

Yea, exactly, we're currently focused on the v1.0.0 release and a couple of other higher priorities. That said, providing a solution for the routing issue is very much on the radar (it's also usefull for other use cases). And the typing issue is relatively easy to solve.

(If someone needs this and is willing to sponsor, then we're definitely open to bump the priority.)