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 🙏

© 2025 – Pkg Stats / Ryan Hefner

eslint-plugin-no-link-component

v0.0.1

Published

This ESLint rule checks your JSX for <Link /> components and outputs an error if it finds one

Downloads

6

Readme

eslint-plugin-no-link-component

This ESLint rule checks your JSX for components and outputs an error if it finds one. This will be useful if your team uses a wrapped version of React Router's Link component.

This is an example of using a wrapped Link component to handle app updates when a service worker is installed.

Installation

You'll first need to install ESLint:

$ npm i eslint --save-dev

Next, install eslint-plugin-no-link-component:

$ npm install eslint-plugin-no-link-component --save-dev

Note: If you installed ESLint globally, you must also install eslint-plugin-no-link-component globally.

Usage

Add no-link-component to the plugins section of your .eslintrc configuration file. You can omit the eslint-plugin- prefix:

{
    "plugins": [
        "no-link-component"
    ]
}

Then add no-link-component's only rule under the rules section.

{
    "rules": {
        "no-link-component/no-link-component": "error"
    }
}

Rule Details

This rule outputs an error to prevent usage of React Router's Link component (or any component named Link) throughout your app because you're using a wrapped/custom version of it.

The following patterns are considered warnings:

<Link to={`/users/${user.id}`} activeClassName="active">{user.name}</Link>

The following patterns are not warnings:

<CustomLink to={`/users/${user.id}`} activeClassName="active">{user.name}</CustomLink>
<UpdateLink to={`/users/${user.id}`} activeClassName="active">{user.name}</UpdateLink>

Note that you'll want to disable the rule in your CustomLink/UpdateLink definition:

/* eslint-disable consistent-return */