Unverified Commit 73ab7c5d authored by Aurora Scharff's avatar Aurora Scharff Committed by GitHub

docs: update links for transferred demo repositories (#100041)

## Summary

Update documentation links for `async-react-demo` and
`next-spa-patterns` after moving the repositories from `vercel-labs` to
the `nextjs` organization. The existing live demo URLs remain unchanged.

## Verification

- `pnpm prettier --with-node-modules --ignore-path .prettierignore
--write <changed files>`
- `npx eslint --config eslint.config.mjs --fix <changed files>`
- Verified the destination repositories are public under `nextjs`

<!-- NEXT_JS_LLM -->
parent 1d31d04a
...@@ -69,4 +69,4 @@ After a mutation, invalidate any cached server read that provided the initial da ...@@ -69,4 +69,4 @@ After a mutation, invalidate any cached server read that provided the initial da
- [Client-side data fetching with SWR](/docs/app/guides/client-side-data-fetching/swr) - [Client-side data fetching with SWR](/docs/app/guides/client-side-data-fetching/swr)
- [Client-side data fetching with TanStack Query](/docs/app/guides/client-side-data-fetching/tanstack-query) - [Client-side data fetching with TanStack Query](/docs/app/guides/client-side-data-fetching/tanstack-query)
See both patterns in the live [`next-spa-patterns` demo](https://next-spa-patterns.labs.vercel.dev) and its [source code](https://github.com/vercel-labs/next-spa-patterns). See both patterns in the live [`next-spa-patterns` demo](https://next-spa-patterns.labs.vercel.dev) and its [source code](https://github.com/nextjs/next-spa-patterns).
...@@ -429,4 +429,4 @@ The optimistic SWR value updates the current screen. `updateTag` ensures the nex ...@@ -429,4 +429,4 @@ The optimistic SWR value updates the current screen. `updateTag` ensures the nex
> **Good to know:** Call `updateTag` when a Server Action changes a cached read that must reflect the write immediately. An uncached read does not have a server tag to update. See [Client-side data fetching](/docs/app/guides/client-side-data-fetching#coordinate-mutations) for other invalidation behaviors. > **Good to know:** Call `updateTag` when a Server Action changes a cached read that must reflect the write immediately. An uncached read does not have a server tag to update. See [Client-side data fetching](/docs/app/guides/client-side-data-fetching#coordinate-mutations) for other invalidation behaviors.
See the [live `next-spa-patterns` demo](https://next-spa-patterns.labs.vercel.dev/swr) and its [source code](https://github.com/vercel-labs/next-spa-patterns/tree/main/app/swr). Learn more about [SWR mutation and optimistic updates](https://swr.vercel.app/docs/mutation) and the [SWR documentation](https://swr.vercel.app/docs/getting-started). See the [live `next-spa-patterns` demo](https://next-spa-patterns.labs.vercel.dev/swr) and its [source code](https://github.com/nextjs/next-spa-patterns/tree/main/app/swr). Learn more about [SWR mutation and optimistic updates](https://swr.vercel.app/docs/mutation) and the [SWR documentation](https://swr.vercel.app/docs/getting-started).
...@@ -53,7 +53,7 @@ export default function Layout({ children }: LayoutProps<'/products'>) { ...@@ -53,7 +53,7 @@ export default function Layout({ children }: LayoutProps<'/products'>) {
} }
``` ```
See the [complete provider setup in the demo source](https://github.com/vercel-labs/next-spa-patterns/tree/main/app/react-query) or learn about provider options in the [TanStack Query Advanced SSR guide](https://tanstack.com/query/latest/docs/framework/react/guides/advanced-ssr). See the [complete provider setup in the demo source](https://github.com/nextjs/next-spa-patterns/tree/main/app/react-query) or learn about provider options in the [TanStack Query Advanced SSR guide](https://tanstack.com/query/latest/docs/framework/react/guides/advanced-ssr).
## Fetch data on the client ## Fetch data on the client
...@@ -655,4 +655,4 @@ async function ProductData({ id }) { ...@@ -655,4 +655,4 @@ async function ProductData({ id }) {
> **Good to know:** The timestamp must advance whenever the hydrated data changes. The helper suits tag-driven server data because both use the same tags. For time-driven server data, derive the data and hydration timestamp from the same cached snapshot instead of maintaining unrelated time windows. > **Good to know:** The timestamp must advance whenever the hydrated data changes. The helper suits tag-driven server data because both use the same tags. For time-driven server data, derive the data and hydration timestamp from the same cached snapshot instead of maintaining unrelated time windows.
See the [live `next-spa-patterns` demo](https://next-spa-patterns.labs.vercel.dev/react-query) and its [source code](https://github.com/vercel-labs/next-spa-patterns/tree/main/app/react-query). Learn more about [TanStack Query optimistic updates](https://tanstack.com/query/latest/docs/framework/react/guides/optimistic-updates) and the [TanStack Query documentation](https://tanstack.com/query/latest/docs/framework/react/overview). See the [live `next-spa-patterns` demo](https://next-spa-patterns.labs.vercel.dev/react-query) and its [source code](https://github.com/nextjs/next-spa-patterns/tree/main/app/react-query). Learn more about [TanStack Query optimistic updates](https://tanstack.com/query/latest/docs/framework/react/guides/optimistic-updates) and the [TanStack Query documentation](https://tanstack.com/query/latest/docs/framework/react/overview).
...@@ -21,7 +21,7 @@ This guide adds responsive feedback to a task management app called _Taskboard_. ...@@ -21,7 +21,7 @@ This guide adds responsive feedback to a task management app called _Taskboard_.
The patterns build in order: stream slow data behind loading boundaries, add an instant priority toggle, build a reusable filter with a callback prop, show comments before they're confirmed, move cards between columns on drop, manage form lifecycle in a create dialog, and signal pending deletion to a parent. The final step caches the reusable reads so navigations stay instant. The patterns build in order: stream slow data behind loading boundaries, add an instant priority toggle, build a reusable filter with a callback prop, show comments before they're confirmed, move cards between columns on drop, manage form lifecycle in a create dialog, and signal pending deletion to a parent. The final step caches the reusable reads so navigations stay instant.
The companion [Taskboard demo](https://async-react-demo.labs.vercel.dev) ([source](https://github.com/vercel-labs/async-react-demo)) lets you see each pattern from this guide in action. The companion [Taskboard demo](https://async-react-demo.labs.vercel.dev) ([source](https://github.com/nextjs/async-react-demo)) lets you see each pattern from this guide in action.
The app is organized by feature. Everything for the task domain (queries, Server Functions, and components) lives under `features/task/`. Shared UI primitives live in `components/ui/`, and pages in `app/` compose feature components. The file paths throughout this guide follow that structure. The app is organized by feature. Everything for the task domain (queries, Server Functions, and components) lives under `features/task/`. Shared UI primitives live in `components/ui/`, and pages in `app/` compose feature components. The file paths throughout this guide follow that structure.
......
...@@ -34,7 +34,7 @@ Next.js can start as a static site or even a strict SPA where everything is rend ...@@ -34,7 +34,7 @@ Next.js can start as a static site or even a strict SPA where everything is rend
## Build common SPA patterns ## Build common SPA patterns
The following examples cover common patterns for building an SPA with Next.js. The companion [demo](https://next-spa-patterns.labs.vercel.dev) ([source](https://github.com/vercel-labs/next-spa-patterns)) shows each pattern in action. The following examples cover common patterns for building an SPA with Next.js. The companion [demo](https://next-spa-patterns.labs.vercel.dev) ([source](https://github.com/nextjs/next-spa-patterns)) shows each pattern in action.
### Using React's `use` within a Context Provider ### Using React's `use` within a Context Provider
...@@ -200,7 +200,7 @@ export default function Page() { ...@@ -200,7 +200,7 @@ export default function Page() {
The component that consumes the Promise (e.g. `Profile` above) suspends while the Promise resolves, so you see the streamed, prerendered HTML before JavaScript has finished loading. The component that consumes the Promise (e.g. `Profile` above) suspends while the Promise resolves, so you see the streamed, prerendered HTML before JavaScript has finished loading.
See the [live demo](https://next-spa-patterns.labs.vercel.dev/use-context) and its [source code](https://github.com/vercel-labs/next-spa-patterns/tree/main/app/use-context). See the [live demo](https://next-spa-patterns.labs.vercel.dev/use-context) and its [source code](https://github.com/nextjs/next-spa-patterns/tree/main/app/use-context).
### Rendering components only in the browser ### Rendering components only in the browser
...@@ -260,7 +260,7 @@ export default function Page() { ...@@ -260,7 +260,7 @@ export default function Page() {
In the browser, `browser()` returns `undefined`, and the editor renders with the saved draft. In the browser, `browser()` returns `undefined`, and the editor renders with the saved draft.
See both approaches in the [live demo](https://next-spa-patterns.labs.vercel.dev/browser-only). The [demo source](https://github.com/vercel-labs/next-spa-patterns/tree/main/app/browser-only) contains the complete examples. See both approaches in the [live demo](https://next-spa-patterns.labs.vercel.dev/browser-only). The [demo source](https://github.com/nextjs/next-spa-patterns/tree/main/app/browser-only) contains the complete examples.
### Shallow routing on the client ### Shallow routing on the client
...@@ -318,7 +318,7 @@ export default function SortProducts() { ...@@ -318,7 +318,7 @@ export default function SortProducts() {
Learn more about how [routing and navigation](/docs/app/getting-started/linking-and-navigating#how-navigation-works) work in Next.js. Learn more about how [routing and navigation](/docs/app/getting-started/linking-and-navigating#how-navigation-works) work in Next.js.
See the [live demo](https://next-spa-patterns.labs.vercel.dev/shallow-routing) and its [source code](https://github.com/vercel-labs/next-spa-patterns/tree/main/app/shallow-routing). See the [live demo](https://next-spa-patterns.labs.vercel.dev/shallow-routing) and its [source code](https://github.com/nextjs/next-spa-patterns/tree/main/app/shallow-routing).
### Mutating data with Server Actions ### Mutating data with Server Actions
...@@ -569,7 +569,7 @@ export function TodoList({ initialTodos }) { ...@@ -569,7 +569,7 @@ export function TodoList({ initialTodos }) {
The optimistic update shows instantly, while `useActionState`'s pending flag lets you display a subtle indicator (such as `Syncing to server…`) until the Server Action resolves. The optimistic update shows instantly, while `useActionState`'s pending flag lets you display a subtle indicator (such as `Syncing to server…`) until the Server Action resolves.
See the [live demo](https://next-spa-patterns.labs.vercel.dev/mutations) and its [source code](https://github.com/vercel-labs/next-spa-patterns/tree/main/app/mutations). See the [live demo](https://next-spa-patterns.labs.vercel.dev/mutations) and its [source code](https://github.com/nextjs/next-spa-patterns/tree/main/app/mutations).
To learn more about adding interactivity on top of server-rendered apps so they feel like SPAs, see the [Building interactive apps](/docs/app/guides/interactive-apps) guide and its runnable demo. To learn more about adding interactivity on top of server-rendered apps so they feel like SPAs, see the [Building interactive apps](/docs/app/guides/interactive-apps) guide and its runnable demo.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment