mirror of
https://github.com/hanzoai/next.js.git
synced 2026-10-30 14:46:38 +00:00
Andrew ClarkandGitHub
904501127c
**Current:** 1. https://github.com/vercel/next.js/pull/92011 **Up next:** 2. https://github.com/vercel/next.js/pull/92012 --- When a navigation, server action, or prefetch fails due to a network error, instead of falling back to MPA navigation or surfacing an error, the request blocks until connectivity is restored and then retries automatically. Offline detection works by treating any `fetch()` rejection as a network error (server errors resolve with a status code, they don't reject). Once offline, a polling loop does HEAD requests with exponential backoff to detect when connectivity returns. Browser offline/online events also feed into this loop. Successful fetches from other code paths can short-circuit the loop if they happen to land first. Follow-up work will add a `useOffline` hook so apps can show an offline indicator to the user, and allow navigations to read from stale cache entries while offline. Gated behind `experimental.useOffline`.
33 lines
622 B
TypeScript
33 lines
622 B
TypeScript
'use client'
|
|
import Link from 'next/link'
|
|
import { useState } from 'react'
|
|
|
|
export function LinkAccordion({
|
|
href,
|
|
children,
|
|
prefetch,
|
|
}: {
|
|
href: string
|
|
children: React.ReactNode
|
|
prefetch?: boolean
|
|
}) {
|
|
const [isVisible, setIsVisible] = useState(false)
|
|
return (
|
|
<>
|
|
<input
|
|
type="checkbox"
|
|
checked={isVisible}
|
|
onChange={() => setIsVisible(!isVisible)}
|
|
data-link-accordion={href}
|
|
/>
|
|
{isVisible ? (
|
|
<Link href={href} prefetch={prefetch}>
|
|
{children}
|
|
</Link>
|
|
) : (
|
|
`${children} (link is hidden)`
|
|
)}
|
|
</>
|
|
)
|
|
}
|