npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@vividwebau/next-link-no-autoprefetch

v1.0.0

Published

A drop‑in replacement for Next.js `<Link>` with `prefetch={false}` by default. Designed for predictable performance, explicit intent, and strict TypeScript behaviour.

Downloads

1,407

Readme

@vividwebau/next-link-no-autoprefetch

A drop‑in replacement for Next.js <Link> with prefetch={false} by default.
Designed for predictable performance, explicit intent, and strict TypeScript behaviour.


Features

  • autoprefetch disabled unless explicitly enabled
  • identical API to next/link
  • full passthrough of anchor attributes (className, style, id, etc.)
  • strict TypeScript typing
  • optional ESLint rule to enforce explicit prefetch usage
  • Biome‑friendly import restriction pattern
  • tested in a real Next.js app before publish

Installation

pnpm add @vividwebau/next-link-no-autoprefetch

Usage

import Link from "@vividwebau/next-link-no-autoprefetch";

export default function Page() {
  return (
    <Link href="/about" className="nav-item">
      About
    </Link>
  );
}

Enable prefetch explicitly

<Link href="/contact" prefetch>
  Contact
</Link>

Typing

This component merges:

  • LinkProps from next/link
  • AnchorHTMLAttributes<HTMLAnchorElement>
  • children: ReactNode

This ensures correct typing for:

  • className
  • style
  • onClick
  • target
  • rel
  • all other anchor attributes

Biome Users

Biome does not currently support custom lint rules, but you can still enforce usage of this component by restricting imports of next/link.

Add this to your biome.json:

{
  "linter": {
    "enabled": true,
    "rules": {
      "style": {
        "noRestrictedImports": {
          "level": "error",
          "options": {
            "paths": {
              "next/link": "Use @vividwebau/next-link-no-autoprefetch instead"
            }
          }
        }
      }
    }
  }
}

This produces an error whenever next/link is imported.


ESLint Users

Install the companion plugin:

pnpm add -D eslint-plugin-next-link-no-autoprefetch

Add the rule to your ESLint config:

{
  "plugins": ["next-link-no-autoprefetch"],
  "rules": {
    "next-link-no-autoprefetch/no-next-link": "error"
  }
}

This rule prevents accidental usage of next/link:

Invalid

import Link from "next/link";

Valid

import Link from "@vividwebau/next-link-no-autoprefetch";

Use this if your project uses ESLint and you want a hard guarantee that the wrapper is always used.


Vitest Support

This package uses Next.js’s server/client architecture, which works automatically in real Next.js apps.
When testing with Vitest, you may need to tell Vite to transform this package instead of treating it as an external dependency.

Add the following to your vitest.config.ts:

export default defineConfig({
  ssr: {
    noExternal: ["@vividwebau/next-link-no-autoprefetch"],
  },
});


---

## **Test App**

This package is validated in a real Next.js environment located at:

apps/test


The test app ensures:

- correct prop passthrough
- correct typing under strict TS
- correct runtime behaviour
- no regressions before publish

---

## License

MIT © Vivid Web  
This package wraps Next.js's `next/link`, which is also licensed under MIT.