docs: use relative links

Author: posva

docs/.vitepress/config.js

@@ -301,24 +301,6 @@ const config = {
         ],
       },
     },
-
-    // '/es/': {
-    //   nav: [
-    //     {
-    //       text: 'Guía',
-    //       link: '/guide/',
-    //     },
-    //     {
-    //       text: 'API',
-    //       link: '/api/',
-    //     },
-    //     {
-    //       text: 'Cambios',
-    //       link:
-    //         'https://github.com/vuejs/vue-router-next/blob/master/CHANGELOG.md',
-    //     },
-    //   ],
-    // },
   },
 }
 

docs/api/index.md

@@ -154,7 +154,7 @@ If you add a `target="_blank"` to your `a` element, you must omit the `@click="n
 
   When a `<router-view>` has a `name`, it will render the component with the corresponding name in the matched route record's `components` option.
 
-- **See Also**: [Named Views](/guide/essentials/named-views.md)
+- **See Also**: [Named Views](../guide/essentials/named-views.md)
 
 ### route
 
@@ -771,7 +771,7 @@ stringifyQuery?: (
 Route record that can be provided by the user when adding routes via the [`routes` option](#routeroptions) or via [`router.addRoutes()`](#addroutes). There are three different kind of route records:
 
 - Single views records: have a `component` option
-- Multiple views records ([named views](/guide/essentials/named-views.md)): have a `components` option
+- Multiple views records ([named views](../guide/essentials/named-views.md)): have a `components` option
 - Redirect records: cannot have `component` or `components` option because a redirect record is never reached.
 
 ### path
@@ -782,7 +782,7 @@ Route record that can be provided by the user when adding routes via the [`route
   Path of the record. Should start with `/` unless the record is the child of another record.
   Can define parameters: `/users/:id` matches `/users/1` as well as `/users/posva`.
 
-- **See Also**: [Dynamic Route Matching](/guide/essentials/dynamic-matching.md)
+- **See Also**: [Dynamic Route Matching](../guide/essentials/dynamic-matching.md)
 
 ### redirect
 
@@ -801,7 +801,7 @@ Route record that can be provided by the user when adding routes via the [`route
 
   Nested routes of the current record.
 
-- **See Also**: [Nested Routes](/guide/essentials/nested-routes.md)
+- **See Also**: [Nested Routes](../guide/essentials/nested-routes.md)
 
 ### alias
 
@@ -834,7 +834,7 @@ Route record that can be provided by the user when adding routes via the [`route
   Allows passing down params as props to the component rendered by `router-view`. When passed to a _multiple views record_, it should be an object with the same keys as `components` or a `boolean` to be applied to each component.
   target location.
 
-- **See Also**: [Passing props to Route Components](/guide/essentials/passing-props.md)
+- **See Also**: [Passing props to Route Components](../guide/essentials/passing-props.md)
 
 ### meta
 
@@ -843,7 +843,7 @@ Route record that can be provided by the user when adding routes via the [`route
 
   Custom data attached to the record.
 
-- **See Also**: [Meta fields](/guide/advanced/meta.md)
+- **See Also**: [Meta fields](../guide/advanced/meta.md)
 
 ## RouteRecordNormalized
 
@@ -863,7 +863,7 @@ Normalized version of a [Route Record](#routerecordraw)
 
   Navigation guard applied when entering this record from somewhere else.
 
-- **See Also**: [Navigation guards](/guide/advanced/navigation-guards.md)
+- **See Also**: [Navigation guards](../guide/advanced/navigation-guards.md)
 
 ### children
 
@@ -886,7 +886,7 @@ Normalized version of a [Route Record](#routerecordraw)
 
   Arbitrary data attached to the record.
 
-- **See also**: [Meta fields](/guide/advanced/meta.md)
+- **See also**: [Meta fields](../guide/advanced/meta.md)
 
 ### name
 
@@ -918,7 +918,7 @@ Normalized version of a [Route Record](#routerecordraw)
 
 ## RouteLocationRaw
 
-User-level route location that can be passed to `router.push()`, `redirect`, and returned in [Navigation Guards](/guide/advanced/navigation-guards.md).
+User-level route location that can be passed to `router.push()`, `redirect`, and returned in [Navigation Guards](../guide/advanced/navigation-guards.md).
 
 A raw location can either be a `string` like `/users/posva#bio` or an object:
 
@@ -988,7 +988,7 @@ Normalized route location. Does not have any [redirect records](#routerecordraw)
 
   Arbitrary data attached to all matched records merged (non recursively) from parent to child.
 
-- **See also**: [Meta fields](/guide/advanced/meta.md)
+- **See also**: [Meta fields](../guide/advanced/meta.md)
 
 ### name
 
@@ -1041,7 +1041,7 @@ Normalized route location. Does not have any [redirect records](#routerecordraw)
 
   Type of the navigation failure.
 
-- **See Also**: [Navigation Failures](/guide/advanced/navigation-failures.md)
+- **See Also**: [Navigation Failures](../guide/advanced/navigation-failures.md)
 
 ## NavigationGuard
 
@@ -1060,7 +1060,7 @@ Normalized route location. Does not have any [redirect records](#routerecordraw)
   - [`RouteLocationRaw`](#routelocationraw): redirects to a different location
   - `(vm: ComponentPublicInstance) => any` **only for `beforeRouteEnter`**: A callback to be executed once the navigation completes. Receives the route component instance as the parameter.
 
-- **See Also**: [Navigation Guards](/guide/advanced/navigation-guards.md)
+- **See Also**: [Navigation Guards](../guide/advanced/navigation-guards.md)
 
 ## Component Injections
 
@@ -1082,4 +1082,4 @@ These properties are injected into every child component by calling `app.use(rou
 - **beforeRouteUpdate**
 - **beforeRouteLeave**
 
-See [In Component Guards](/guide/advanced/navigation-guards.md#in-component-guards).
+See [In Component Guards](../guide/advanced/navigation-guards.md#in-component-guards).

docs/guide/advanced/composition-api.md

@@ -84,7 +84,7 @@ Composition API guards can also be used in any component rendered by `<router-vi
 
 ## `useLink`
 
-Vue Router exposes the internal behavior of RouterLink as a Composition API function. It gives access the same properties as the [`v-slot` API](/api/#router-link-s-v-slot):
+Vue Router exposes the internal behavior of RouterLink as a Composition API function. It gives access the same properties as the [`v-slot` API](../../api/#router-link-s-v-slot):
 
 ```js
 import { RouterLink, useLink } from 'vue-router'

docs/guide/advanced/dynamic-routing.md

@@ -1,6 +1,6 @@
 # Dynamic Routing
 
-Adding routes to your router is usually done via the [`routes` option](/api/#routes) but in some situations, you might want to add or remove routes while the application is already running. Application with extensible interfaces like [Vue CLI UI](https://cli.vuejs.org/dev-guide/ui-api.html) can use this to make the application grow.
+Adding routes to your router is usually done via the [`routes` option](../../api/#routes) but in some situations, you might want to add or remove routes while the application is already running. Application with extensible interfaces like [Vue CLI UI](https://cli.vuejs.org/dev-guide/ui-api.html) can use this to make the application grow.
 
 ## Adding Routes
 
@@ -99,5 +99,5 @@ router.addRoute({
 
 Vue Router gives you two functions to look at existing routes:
 
-- [`router.hasRoute()`](/api/#hasroute): check if a route exists
-- [`router.getRoutes()`](/api/#getroutes): get an array with all the route records.
+- [`router.hasRoute()`](../../api/#hasroute): check if a route exists
+- [`router.getRoutes()`](../../api/#getroutes): get an array with all the route records.

docs/guide/advanced/navigation-guards.md

@@ -20,15 +20,15 @@ Global before guards are called in creation order, whenever a navigation is trig
 
 Every guard function receives two arguments:
 
-- **`to`**: the target route location [in a normalized format](/api/#routelocationnormalized) being navigated to.
-- **`from`**: the current route location [in a normalized format](/api/#routelocationnormalized) being navigated away from.
+- **`to`**: the target route location [in a normalized format](../../api/#routelocationnormalized) being navigated to.
+- **`from`**: the current route location [in a normalized format](../../api/#routelocationnormalized) being navigated away from.
 
 And can optionally return any of the following values:
 
 - `false`: cancel the current navigation. If the browser URL was changed (either manually by the user or via back button), it will be reset to that of the `from` route.
-- A [Route Location](/api/#routelocationraw): Redirect to a different location by passing a route location as if you were calling [`router.push()`](/api/#push), which allows you to pass options like `replace: true` or `name: 'home'`. The current navigation is dropped and a new one is created with the same `from`.
+- A [Route Location](../../api/#routelocationraw): Redirect to a different location by passing a route location as if you were calling [`router.push()`](../../api/#push), which allows you to pass options like `replace: true` or `name: 'home'`. The current navigation is dropped and a new one is created with the same `from`.
 
-It's also possible to throw an `Error` if an unexpected situation was met. This will also cancel the navigation and call any callback registered via [`router.onError()`](/api/#onerror).
+It's also possible to throw an `Error` if an unexpected situation was met. This will also cancel the navigation and call any callback registered via [`router.onError()`](../../api/#onerror).
 
 If nothing, `undefined` or `true` is returned, **the navigation is validated**, and the next navigation guard is called.
 

docs/guide/advanced/transitions.md

@@ -1,6 +1,6 @@
 # Transitions
 
-In order to use transitions on your route components and animate navigations, you need to use the [v-slot API](/api/#router-view-s-v-slot):
+In order to use transitions on your route components and animate navigations, you need to use the [v-slot API](../../api/#router-view-s-v-slot):
 
 ```html
 <router-view v-slot="{ Component }">

docs/guide/essentials/dynamic-matching.md

@@ -31,7 +31,7 @@ You can have multiple _params_ in the same route, and they will map to correspon
 | /users/:username               | /users/eduardo           | `{ username: 'eduardo' }`                |
 | /users/:username/posts/:postId | /users/eduardo/posts/123 | `{ username: 'eduardo', postId: '123' }` |
 
-In addition to `$route.params`, the `$route` object also exposes other useful information such as `$route.query` (if there is a query in the URL), `$route.hash`, etc. You can check out the full details in the [API Reference](/api/#routelocationnormalized).
+In addition to `$route.params`, the `$route` object also exposes other useful information such as `$route.query` (if there is a query in the URL), `$route.hash`, etc. You can check out the full details in the [API Reference](../../api/#routelocationnormalized).
 
 A working demo of this example can be found [here](https://codesandbox.io/s/route-params-vue-router-examples-mlb14?from-embed&initialpath=%2Fusers%2Feduardo%2Fposts%2F1).
 
@@ -88,7 +88,7 @@ const routes = [
 ]
 ```
 
-In this specific scenario we are using a [custom regexp](/guide/essentials/route-matching-syntax.md#custom-regexp-in-params) between parentheses and marking the `pathMatch` param as [optionally repeatable](/guide/essentials/route-matching-syntax.md#optional-parameters). This allows us to directly navigate to the route if we need to by splitting the `path` into an array:
+In this specific scenario we are using a [custom regexp](./route-matching-syntax.md#custom-regexp-in-params) between parentheses and marking the `pathMatch` param as [optionally repeatable](./route-matching-syntax.md#optional-parameters). This allows us to directly navigate to the route if we need to by splitting the `path` into an array:
 
 ```js
 this.$router.push({
@@ -101,7 +101,7 @@ this.$router.push({
 })
 ```
 
-See more in the [repeated params](/guide/essentials/route-matching-syntax.md#repeatable-params) section.
+See more in the [repeated params](./route-matching-syntax.md#repeatable-params) section.
 
 If you are using [History mode](./history-mode.md), make sure to follow the instructions to correctly configure your server as well.
 

docs/guide/essentials/history-mode.md

@@ -42,7 +42,7 @@ Not to worry: To fix the issue, all you need to do is add a simple catch-all fal
 
 ## Example Server Configurations
 
-**Note**: The following examples assume you are serving your app from the root folder. If you deploy to a subfolder, you should use [the `publicPath` option of Vue CLI](https://cli.vuejs.org/config/#publicpath) and the related [`base` property of the router](/api/#createwebhistory). You also need to adjust the examples below to use the subfolder instead of the root folder (e.g. replacing `RewriteBase /` with `RewriteBase /name-of-your-subfolder/`).
+**Note**: The following examples assume you are serving your app from the root folder. If you deploy to a subfolder, you should use [the `publicPath` option of Vue CLI](https://cli.vuejs.org/config/#publicpath) and the related [`base` property of the router](../../api/#createwebhistory). You also need to adjust the examples below to use the subfolder instead of the root folder (e.g. replacing `RewriteBase /` with `RewriteBase /name-of-your-subfolder/`).
 
 ### Apache
 

docs/guide/essentials/navigation.md

@@ -53,7 +53,7 @@ router.push({ path: '/user', params: { username } }) // -> /user
 
 Since the prop `to` accepts the same kind of object as `router.push`, the exact same rules apply to both of them.
 
-`router.push` and all the other navigation methods return a _Promise_ that allows us to wait til the navigation is finished and to know if it succeeded or failed. We will talk more about that in [Navigation Handling](../advanced/navigation-handling.md).
+`router.push` and all the other navigation methods return a _Promise_ that allows us to wait til the navigation is finished and to know if it succeeded or failed. We will talk more about that in [Navigation Handling](../advanced/navigation-failures.md).
 
 ## Replace current location
 
@@ -98,4 +98,4 @@ You may have noticed that `router.push`, `router.replace` and `router.go` are co
 
 Therefore, if you are already familiar with [Browser History APIs](https://developer.mozilla.org/en-US/docs/Web/API/History_API), manipulating history will feel familiar when using Vue Router.
 
-It is worth mentioning that Vue Router navigation methods (`push`, `replace`, `go`) work consistently no matter the kind of [`history` option](/api/#history) is passed when creating the router instance.
+It is worth mentioning that Vue Router navigation methods (`push`, `replace`, `go`) work consistently no matter the kind of [`history` option](../../api/#history) is passed when creating the router instance.

docs/guide/index.md

@@ -90,6 +90,6 @@ export default {
 }
 ```
 
-To access the router or the route inside the `setup` function, call the `useRouter` or `useRoute` functions. We will learn more about this in [the Composition API](/guide/advanced/composition-api.md#accessing-the-router-and-current-route-inside-setup)
+To access the router or the route inside the `setup` function, call the `useRouter` or `useRoute` functions. We will learn more about this in [the Composition API](./advanced/composition-api.md#accessing-the-router-and-current-route-inside-setup)
 
 Throughout the docs, we will often use the `router` instance. Keep in mind that `this.$router` is exactly the same as directly using the `router` instance created through `createRouter`. The reason we use `this.$router` is because we don't want to import the router in every single component that needs to manipulate routing.

docs/guide/migration/index.md

@@ -163,7 +163,7 @@ app.config.globalProperties.append = (path, pathToAppend) =>
 
 ### Removal of `event` and `tag` props in `<router-link>`
 
-Both `event`, and `tag` props have been removed from `<router-link>`. You can use the [`v-slot` API](/api/#router-link-s-v-slot) to fully customize `<router-link>`:
+Both `event`, and `tag` props have been removed from `<router-link>`. You can use the [`v-slot` API](../../api/#router-link-s-v-slot) to fully customize `<router-link>`:
 
 ```html
 replace
@@ -193,7 +193,7 @@ At the moment navigation guards in mixins are not supported. You can track its s
 
 ### Removal of `router.match` and changes to `router.resolve`
 
-Both `router.match`, and `router.resolve` have been merged together into `router.resolve` with a slightly different signature. [Refer to the API](/api/#resolve) for more details.
+Both `router.match`, and `router.resolve` have been merged together into `router.resolve` with a slightly different signature. [Refer to the API](../../api/#resolve) for more details.
 
 **Reason**: Uniting multiple methods that were used for the same purpose.
 
@@ -354,7 +354,11 @@ const routes = [
     component: DashboardParent,
     children: [
       { path: '', name: 'dashboard', component: DashboardDefault },
-      { path: 'settings', name: 'dashboard-settings', component: DashboardSettings },
+      {
+        path: 'settings',
+        name: 'dashboard-settings',
+        component: DashboardSettings,
+      },
     ],
   },
 ]
@@ -384,7 +388,7 @@ const routes = [
 
 Note this will work if `path` was `/parent/` as the relative location `home` to `/parent/` is indeed `/parent/home` but the relative location of `home` to `/parent` is `/home`.
 
-<!-- Learn more about relative links [in the cookbook](/cookbook/relative-links.md). -->
+<!-- Learn more about relative links [in the cookbook](../../cookbook/relative-links.md). -->
 
 **Reason**: This is to make trailing slash behavior consistent: by default all routes allow a trailing slash. It can be disabled by using the `strict` option and manually appending (or not) a slash to the routes.
 
@@ -394,10 +398,10 @@ Note this will work if `path` was `/parent/` as the relative location `home` to
 
 Decoded values in `params`, `query`, and `hash` are now consistent no matter where the navigation is initiated (older browsers will still produce unencoded `path` and `fullPath`). The initial navigation should yield the same results as in-app navigations.
 
-Given any [normalized route location](/api/#routelocationnormalized):
+Given any [normalized route location](../../api/#routelocationnormalized):
 
 - Values in `path`, `fullPath` are not decoded anymore. They will appear as provided by the browser (most browsers provide them encoded). e.g. directly writing on the address bar `https://example.com/hello world` will yield the encoded version: `https://example.com/hello%20world` and both `path` and `fullPath` will be `/hello%20world`.
-- `hash` is now decoded, that way it can be copied over: `router.push({ hash: $route.hash })` and be used directly in [scrollBehavior](/api/#scrollbehavior)'s `el` option.
+- `hash` is now decoded, that way it can be copied over: `router.push({ hash: $route.hash })` and be used directly in [scrollBehavior](../../api/#scrollbehavior)'s `el` option.
 - When using `push`, `resolve`, and `replace` and providing a `string` location or a `path` property in an object, **it must be encoded** (like in the previous version). On the other hand, `params`, `query` and `hash` must be provided in its unencoded version.
 - The slash character (`/`) is now properly decoded inside `params` while still producing an encoded version on the URL: `%2F`.
 
@@ -417,6 +421,6 @@ To make typings more consistent and expressive, some types have been renamed:
 
 Some of new features to keep an eye on in Vue Router 4 include:
 
-- [Dynamic Routing](/api/#addroute-2)
-- [Composition API](/guide/advanced/composition-api.md)
+- [Dynamic Routing](../../api/#addroute-2)
+- [Composition API](../advanced/composition-api.md)
 <!-- - Custom History implementation -->

docs/introduction.md

@@ -13,7 +13,7 @@ Vue Router is the official router for [Vue.js](http://v3.vuejs.org). It deeply i
 - Customizable Scroll Behavior
 - Proper encoding for URLs
 
-[Get started](/guide/) or play with the [playground](https://github.com/vuejs/vue-router-next/tree/master/playground) (see [`README.md`](https://github.com/vuejs/vue-router-next) to run them).
+[Get started](./guide/) or play with the [playground](https://github.com/vuejs/vue-router-next/tree/master/playground) (see [`README.md`](https://github.com/vuejs/vue-router-next) to run them).
 
 <HomeSponsors />