wip: vapor mode

[zhiyuanzmj]

Description

This PR provide two vapor components: VaporRouterView and VaporRouterLink.
I'm not sure whether we should provide a vue-router/vapor for users to make migration easier.

import { RouterView } from 'vue-router/vapor'

export default () => <RouterView />

The access globalProperties warning should be remove.

• fix(runtime-vapor): remove access globalProperties warning core#13609

Playground

https://repl.zmjs.dev/vuejs/vue-router

TODO

• Tests
• Playground

[netlify]

✅ Deploy Preview for vue-router canceled.

Name	Link
🔨 Latest commit	02a3c5b
🔍 Latest deploy log	https://app.netlify.com/projects/vue-router/deploys/6870ba9b6c9d6000087019da

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/vue-router@2509

commit: 02a3c5b

[posva]

Note for myself for refactoring and simplification: Playground

[Reinhard-Berger]

Is this already compatible with “3.6.0-alpha.1”?
Or is there still work required? I’d be happy to help if I can.

[zhiyuanzmj]

Is this already compatible with “3.6.0-alpha.1”? Or is there still work required? I’d be happy to help if I can.

You can try it in [email protected]

[absidue]

The automatic global registration of the virtual DOM RouterView and RouterLink components in the install hook should probably be removed so that they can be tree-shaken when an app is only using the Vapor ones.

[posva]

FYI this is planned after #2415 which will also allow to register a custom RouterView and RouterLink