Skip to content

Commit dc69e26

Browse files
danielroedanielroe
authored
docs: fix more links (#33265)
1 parent ad97d19 commit dc69e26

32 files changed

+71
-58
lines changed

‎docs/1.getting-started/03.configuration.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -158,7 +158,7 @@ Here is a list of other common config files:
158158

159159
Name | Config File | How To Configure
160160
---------------------------------------------|-------------------------|--------------------------
161-
[TypeScript](https://www.typescriptlang.org) | `tsconfig.json` | [More Info](/docs/4.x/guide/concepts/typescript#nuxttsconfigjson)
161+
[TypeScript](https://www.typescriptlang.org) | `tsconfig.json` | [More Info](/docs/4.x/guide/directory-structure/tsconfig)
162162
[ESLint](https://eslint.org) | `eslint.config.js` | [More Info](https://eslint.org/docs/latest/use/configure/configuration-files)
163163
[Prettier](https://prettier.io) | `prettier.config.js` | [More Info](https://prettier.io/docs/en/configuration.html)
164164
[Stylelint](https://stylelint.io) | `stylelint.config.js` | [More Info](https://stylelint.io/user-guide/configure)

‎docs/1.getting-started/05.assets.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -44,5 +44,5 @@ For example, referencing an image file that will be processed if a build tool is
4444
```
4545

4646
::note
47-
Nuxt won't serve files in the [`app/assets/`](/docs/4.x/guide/directory-structure/app/assets) directory at a static URL like `/assets/my-file.png`. If you need a static URL, use the [`public/`](#public-directory) directory.
47+
Nuxt won't serve files in the [`app/assets/`](/docs/4.x/guide/directory-structure/app/assets) directory at a static URL like `/assets/my-file.png`. If you need a static URL, use the [`public/`](/docs/getting-started/assets#public-directory) directory.
4848
::

‎docs/1.getting-started/08.seo-meta.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ export default defineNuxtConfig({
3333
})
3434
```
3535

36-
You can also provide any of the keys listed below in [Types](#types).
36+
You can also provide any of the keys listed below in [Types](/docs/getting-started/seo-meta#types).
3737

3838
### Defaults Tags
3939

‎docs/1.getting-started/09.transitions.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -415,9 +415,9 @@ Remember, this page transition cannot be overridden with `definePageMeta` on ind
415415

416416
Nuxt ships with an experimental implementation of the [**View Transitions API**](https://developer.chrome.com/docs/web-platform/view-transitions) (see [MDN](https://developer.mozilla.org/en-US/docs/Web/API/View_Transitions_API)). This is an exciting new way to implement native browser transitions which (among other things) have the ability to transition between unrelated elements on different pages.
417417

418-
You can check a demo on https://nuxt-view-transitions.surge.sh and the [source on StackBlitz](https://stackblitz.com/edit/nuxt-view-transitions).
418+
You can check a demo [on StackBlitz](https://stackblitz.com/edit/nuxt-view-transitions).
419419

420-
The Nuxt integration is under active development, but can be enabled with the `experimental.viewTransition` option in your configuration file:
420+
The Nuxt integration can be enabled with the `experimental.viewTransition` option in your configuration file:
421421

422422
```ts twoslash [nuxt.config.ts]
423423
export default defineNuxtConfig({

‎docs/1.getting-started/10.data-fetching.md‎

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -80,8 +80,8 @@ async function addTodo() {
8080
```
8181

8282
::warning
83-
Beware that using only `$fetch` will not provide [network calls de-duplication and navigation prevention](#the-need-for-usefetch-and-useasyncdata). :br
84-
It is recommended to use `$fetch` for client-side interactions (event-based) or combined with [`useAsyncData`](#useasyncdata) when fetching the initial component data.
83+
Beware that using only `$fetch` will not provide [network calls de-duplication and navigation prevention](/docs/getting-started/data-fetching#the-need-for-usefetch-and-useasyncdata). :br
84+
It is recommended to use `$fetch` for client-side interactions (event-based) or combined with [`useAsyncData`](/docs/getting-started/data-fetching#useasyncdata) when fetching the initial component data.
8585
::
8686

8787
::read-more{to="/docs/api/utils/dollarfetch"}
@@ -307,7 +307,7 @@ const { status, data: comments } = useFetch('/api/comments', {
307307
})
308308
```
309309

310-
The `useFetch` composable is meant to be invoked in setup method or called directly at the top level of a function in lifecycle hooks, otherwise you should use [`$fetch` method](#fetch).
310+
The `useFetch` composable is meant to be invoked in setup method or called directly at the top level of a function in lifecycle hooks, otherwise you should use [`$fetch` method](/docs/getting-started/data-fetching#fetch).
311311

312312
### Minimize payload size
313313

@@ -431,7 +431,7 @@ const { data, error, execute, refresh } = await useFetch('/api/users')
431431
</template>
432432
```
433433

434-
The `execute` function is an alias for `refresh` that works in exactly the same way but is more semantic for cases when the fetch is [not immediate](#not-immediate).
434+
The `execute` function is an alias for `refresh` that works in exactly the same way but is more semantic for cases when the fetch is [not immediate](/docs/getting-started/data-fetching#not-immediate).
435435

436436
::tip
437437
To globally refetch or invalidate cached data, see [`clearNuxtData`](/docs/4.x/api/utils/clear-nuxt-data) and [`refreshNuxtData`](/docs/4.x/api/utils/refresh-nuxt-data).
@@ -479,7 +479,7 @@ const { data, error, refresh } = await useFetch(`/api/users/${id.value}`, {
479479
</script>
480480
```
481481

482-
If you need to change the URL based on a reactive value, you may want to use a [computed URL](#computed-url) instead.
482+
If you need to change the URL based on a reactive value, you may want to use a [computed URL](/docs/getting-started/data-fetching#computed-url) instead.
483483

484484
#### Computed URL
485485

@@ -499,7 +499,7 @@ const { data, status } = useLazyFetch('/api/user', {
499499

500500
In the case of more complex URL construction, you may use a callback as a [computed getter](https://vuejs.org/guide/essentials/computed.html) that returns the URL string.
501501

502-
Every time a dependency changes, the data will be fetched using the newly constructed URL. Combine this with [not-immediate](#not-immediate), and you can wait until the reactive element changes before fetching.
502+
Every time a dependency changes, the data will be fetched using the newly constructed URL. Combine this with [not-immediate](/docs/getting-started/data-fetching#not-immediate), and you can wait until the reactive element changes before fetching.
503503

504504
```vue
505505
<script setup lang="ts">
@@ -532,7 +532,7 @@ const pending = computed(() => status.value === 'pending');
532532
</template>
533533
```
534534

535-
If you need to force a refresh when other reactive values change, you can also [watch other values](#watch).
535+
If you need to force a refresh when other reactive values change, you can also [watch other values](/docs/getting-started/data-fetching#watch).
536536

537537
### Not immediate
538538

‎docs/1.getting-started/12.error-handling.md‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ This includes:
5353

5454
## Nitro Server Errors
5555

56-
You cannot currently define a server-side handler for these errors, but can render an error page, see the [Render an Error Page](#error-page) section.
56+
You cannot currently define a server-side handler for these errors, but can render an error page, see the [Render an Error Page](/docs/getting-started/error-handling#error-page) section.
5757

5858
## Errors with JS Chunks
5959

@@ -126,7 +126,7 @@ Make sure to check before using anything dependent on Nuxt plugins, such as `$ro
126126
::
127127

128128
::note
129-
Rendering an error page is an entirely separate page load, meaning any registered middleware will run again. You can use [`useError`](#useerror) in middleware to check if an error is being handled.
129+
Rendering an error page is an entirely separate page load, meaning any registered middleware will run again. You can use [`useError`](/docs/getting-started/error-handling#useerror) in middleware to check if an error is being handled.
130130
::
131131

132132
::note
@@ -156,7 +156,7 @@ function createError (err: string | { cause, data, message, name, stack, statusC
156156
Create an error object with additional metadata. You can pass a string to be set as the error `message` or an object containing error properties. It is usable in both the Vue and Server portions of your app, and is meant to be thrown.
157157

158158
If you throw an error created with `createError`:
159-
- on server-side, it will trigger a full-screen error page which you can clear with [`clearError`](#clearerror).
159+
- on server-side, it will trigger a full-screen error page which you can clear with [`clearError`](/docs/getting-started/error-handling#clearerror).
160160
- on client-side, it will throw a non-fatal error for you to handle. If you need to trigger a full-screen error page, then you can do this by setting `fatal: true`.
161161

162162
```vue twoslash [pages/movies/[slug\\].vue]
@@ -183,7 +183,7 @@ Read more about `createError` util.
183183
function showError (err: string | Error | { statusCode, statusMessage }): Error
184184
```
185185

186-
You can call this function at any point on client-side, or (on server side) directly within middleware, plugins or `setup()` functions. It will trigger a full-screen error page which you can clear with [`clearError`](#clearerror).
186+
You can call this function at any point on client-side, or (on server side) directly within middleware, plugins or `setup()` functions. It will trigger a full-screen error page which you can clear with [`clearError`](/docs/getting-started/error-handling#clearerror).
187187

188188
It is recommended instead to use `throw createError()`.
189189

‎docs/1.getting-started/17.testing.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -624,7 +624,7 @@ Please use the options below for the `setup` method.
624624
- Type: `number | undefined`
625625
- Default: `undefined`
626626

627-
- `host`: If provided, a URL to use as the test target instead of building and running a new server. Useful for running "real" end-to-end tests against a deployed version of your application, or against an already running local server (which may provide a significant reduction in test execution timings). See the [target host end-to-end example below](#target-host-end-to-end-example).
627+
- `host`: If provided, a URL to use as the test target instead of building and running a new server. Useful for running "real" end-to-end tests against a deployed version of your application, or against an already running local server (which may provide a significant reduction in test execution timings). See the [target host end-to-end example below](/docs/getting-started/testing#target-host-end-to-end-example).
628628
- Type: `string`
629629
- Default: `undefined`
630630

‎docs/2.guide/1.concepts/1.auto-imports.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -139,7 +139,7 @@ export default defineNuxtConfig({
139139
})
140140
```
141141

142-
This will disable auto-imports completely but it's still possible to use [explicit imports](#explicit-imports) from `#imports`.
142+
This will disable auto-imports completely but it's still possible to use [explicit imports](/docs/guide/concepts/auto-imports#explicit-imports) from `#imports`.
143143

144144
### Partially Disabling Auto-imports
145145

‎docs/2.guide/1.concepts/3.rendering.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: 'Rendering Modes'
33
description: 'Learn about the different rendering modes available in Nuxt.'
44
---
55

6-
Nuxt supports different rendering modes, [universal rendering](#universal-rendering), [client-side rendering](#client-side-rendering) but also offers [hybrid-rendering](#hybrid-rendering) and the possibility to render your application on [CDN Edge Servers](#edge-side-rendering).
6+
Nuxt supports different rendering modes, [universal rendering](/docs/guide/concepts/rendering#universal-rendering), [client-side rendering](/docs/guide/concepts/rendering#client-side-rendering) but also offers [hybrid-rendering](/docs/guide/concepts/rendering#hybrid-rendering) and the possibility to render your application on [CDN Edge Servers](/docs/guide/concepts/rendering#edge-side-rendering).
77

88
Both the browser and server can interpret JavaScript code to turn Vue.js components into HTML elements. This step is called **rendering**. Nuxt supports both **universal** and **client-side** rendering. The two approaches have benefits and downsides that we will cover.
99

@@ -50,7 +50,7 @@ On the initial request, the `counter` ref is initialized in the server since it
5050

5151
**Downsides of server-side rendering:**
5252
- **Development constraints:** Server and browser environments don't provide the same APIs, and it can be tricky to write code that can run on both sides seamlessly. Fortunately, Nuxt provides guidelines and specific variables to help you determine where a piece of code is executed.
53-
- **Cost:** A server needs to be running in order to render pages on the fly. This adds a monthly cost like any traditional server. However, the server calls are highly reduced thanks to universal rendering with the browser taking over on client-side navigation. A cost reduction is possible by leveraging [edge-side-rendering](#edge-side-rendering).
53+
- **Cost:** A server needs to be running in order to render pages on the fly. This adds a monthly cost like any traditional server. However, the server calls are highly reduced thanks to universal rendering with the browser taking over on client-side navigation. A cost reduction is possible by leveraging [edge-side-rendering](/docs/guide/concepts/rendering#edge-side-rendering).
5454

5555
Universal rendering is very versatile and can fit almost any use case, and is especially appropriate for any content-oriented websites: **blogs, marketing websites, portfolios, e-commerce sites, and marketplaces.**
5656

‎docs/2.guide/1.concepts/4.server-engine.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ It is shipped with many features:
1616

1717
## API Layer
1818

19-
Server [API endpoints](/docs/4.x/guide/directory-structure/server#api-routes) and [Middleware](/docs/4.x/guide/directory-structure/server#server-middleware) are added by Nitro that internally uses [h3](https://github.com/h3js/h3).
19+
Server [API endpoints](/docs/4.x/guide/directory-structure/server#server-routes) and [Middleware](/docs/4.x/guide/directory-structure/server#server-middleware) are added by Nitro that internally uses [h3](https://github.com/h3js/h3).
2020

2121
Key features include:
2222

0 commit comments

Comments
 (0)