---
package: "@webjsdev/core"
version: 0.7.4
date: 2026-06-01T12:00:00+05:30
commit_count: 1
---
## Features

- **Automatic link prefetch in the client router** ([#160](https://github.com/webjsdev/webjs/pull/160)) [`7420f60`](https://github.com/webjsdev/webjs/commit/7420f60)
  Internal `<a href>` links now prefetch on intent (hover, focus, or
  touchstart) by default, so the destination is usually already in cache by
  the time the click lands and navigation feels instant. Strategy is
  controlled per link with a Next-style `data-prefetch` attribute:
  `intent` (default), `render` (warm as soon as the link renders),
  `viewport` (warm when the link scrolls into view), or `none` to opt out.
  The aliases `true` / `false` / `auto` map to `render` / `none` / `intent`
  to match Next's `prefetch` prop values. Only same-origin GET-idempotent
  links are eligible; cross-origin links, `download`, `target=_blank`, and
  anchors carrying a `rel` the framework should not second-guess are left
  untouched, as is the native `<link rel=prefetch>` mechanism. Prefetches
  ride a bounded FIFO queue (concurrency cap, LRU eviction, TTL) and are
  suppressed under `Save-Data` / `prefers-reduced-data`. The prefetch cache
  is evicted on any mutation (`revalidate()`, non-GET form submission) so a
  warmed snapshot can never serve stale post-write content.
