Skip to content

Commit

Permalink
chore(docs): fix broken link (#53021)
Browse files Browse the repository at this point in the history
This link is failing CI as seen here:

https://github.com/vercel/next.js/actions/runs/5623454975/job/15238167610


```
Error: The action could not create a Github comment because it is initiated from a forked repo. View the action logs for a list of broken links.
This PR introduces broken links to the docs:
┌─────────┬───────────────────────────────────────────────────────────────────────────────┬──────┬─────────────────────────────────────────────────────────────────────────────────────┐
│ (index) │                                     link                                      │ type │                                       docPath                                       │
├─────────┼───────────────────────────────────────────────────────────────────────────────┼──────┼─────────────────────────────────────────────────────────────────────────────────────┤
│    0    │ 'app/building-your-application/configuring/typescript#statically-typed-links' │      │ 'docs/02-app/01-building-your-application/01-routing/03-linking-and-navigating.mdx' │
└─────────┴───────────────────────────────────────────────────────────────────────────────┴──────┴─────────────────────────────────────────────────────────────────────────────────────┘
Error: This PR introduces broken links to the docs. The action could not create a Github check because it is initiated from a forked repo.
Error: Process completed with exit code 1.
```
  • Loading branch information
styfle committed Jul 21, 2023
1 parent e4b6c4e commit 26a57af
Showing 1 changed file with 1 addition and 1 deletion.
Expand Up @@ -4,7 +4,7 @@ description: Learn how navigation works in Next.js, and how to use the Link Comp
related:
description: Learn more about statically typed links with TypeScript.
links:
- app/building-your-application/configuring/typescript#statically-typed-links
- app/building-your-application/configuring/typescript
---

The Next.js router uses [server-centric routing](/docs/app/building-your-application/routing#server-centric-routing-with-client-side-navigation) with [client-side navigation](#how-navigation-works). It supports [instant loading states](/docs/app/building-your-application/routing/loading-ui-and-streaming) and [concurrent rendering](https://react.dev/reference/react/startTransition). This means navigation maintains client-side state, avoids expensive re-renders, is interruptible, and doesn't cause race conditions.
Expand Down

0 comments on commit 26a57af

Please sign in to comment.