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 πŸ™

Β© 2024 – Pkg Stats / Ryan Hefner

@bradgarropy/next-link

v1.1.0

Published

πŸ”— link component for next

Downloads

357

Readme

πŸ”— next link

version downloads size github actions coverage typescript contributing contributors discord

πŸ”— link component for next

Next provides a <Link> component for routing between internal pages. For external links, you have to use a regular <a> tag. This next-link package solves that issue by providing a <Link> component that handles both internal and external urls.

πŸ“¦ Installation

This package is hosted on npm.

npm install @bradgarropy/next-link

πŸ₯‘ Usage

For both internal and external links, use the Link component and pass it a to prop.

import Link from "@bradgarropy/next-link"

const App = () => {
    return <Link to="https://bradgarropy.com">website</Link>
}

πŸ“– API Reference

<Link>

| Name | Required | Default | Example | Description | | :--- | :------: | :-----: | :----------------------------------------- | :------------------------ | | to | true | | "/home" "https://bradgarropy.com" | Internal or external url. |

The component also passes through all other props, like className or passHref. See the next/link documentation for other relevant props. The examples below cover some common uses.

// internal link
<Link to="/home">home</Link>

// internal link with additional props
<Link to="/home" className="nav-link">home</Link>

// external link
<Link to="https://bradgarropy.com">website</Link>

// external link with additional props
<Link to="https://bradgarropy.com" className="nav-link">website</Link>

❔ Questions

πŸ› report bugs by filing issues
πŸ“’ provide feedback with issues or on twitter
πŸ™‹πŸΌβ€β™‚οΈ use my ama or twitter to ask any other questions

✨ contributors