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

eslint-plugin-restrict-replace-import

v2.0.1

Published

ESLint Plugin for Restricting and Replacing Import

Downloads

268

Readme

eslint-plugin-restrict-replace-import

ESLint Plugin for Restricting and Replacing Import.

Automatically fixable with replacement package!

Installation

You'll first need to install ESLint:

npm i eslint --save-dev

Next, install eslint-plugin-restrict-replace-import:

npm install eslint-plugin-restrict-replace-import --save-dev

Usage

ESLint v9+ (Flat Config)

// eslint.config.js
import restrictReplaceImport from 'eslint-plugin-restrict-replace-import'

export default [
  {
    plugins: {
      'restrict-replace-import': restrictReplaceImport,
    },
    rules: {
      'restrict-replace-import/restrict-import': [
        'error',
        ['restricted-package1', 'restricted-package2'],
      ],
    },
  },
]

ESLint v8 (Legacy Config)

Add restrict-replace-import to the plugins section of your .eslintrc configuration file. You can omit the eslint-plugin- prefix:

{
  "plugins": ["restrict-replace-import"],
  "rules": {
    "restrict-replace-import/restrict-import": ["error", ["restricted-package1", "restricted-package2"]]
  }
}

Rule Options

You can also specify an alternative package to import instead:

{
  "rules": {
    "restrict-replace-import/restrict-import": [
      "error",
      [
        {
          "target": "restricted-package1",
          "replacement": "replacement-package1"
        },
        {
          "target": "restricted-package2",
          "replacement": "replacement-package2"
        }
      ]
    ]
  }
}

You can use RegExp for package name:

{
  "rules": {
    "restrict-replace-import/restrict-import": [
      "error",
      [
        "with(?:-regex)?-support",
        {
          "target": "restricted-.*",
          "replacement": "replacement-package"
        }
      ]
    ]
  }
}

It is possible as well to perform multiple partial replacements by setting an Object in the replacement property:

{
  "rules": {
    "restrict-replace-import/restrict-import": [
      "error",
      [
        {
          "target": "with-partial-.*",
          "replacement": {
            "par(regExp)?tial-": "successfully-",
            "repla(regExp)?cements": "replaced",
            "with-": ""
          }
        }
      ]
    ]
  }
}

Given that rule configuration it will perform the following replacement:

Input:

import { useState } from 'with-partial-replacements'

Output:

import { useState } from 'successfully-replaced'

You can also restrict specific named imports from a package while allowing others:

{
  "rules": {
    "restrict-replace-import/restrict-import": [
      "error",
      [
        {
          "target": "restricted-module",
          "namedImports": ["restrictedImport", "alsoRestricted"],
          "replacement": "replacement-module"
        }
      ]
    ]
  }
}

This configuration will:

  • Allow: import { allowedImport } from 'restricted-module'
  • Replace: import { restrictedImport } from 'restricted-module'import { restrictedImport } from 'replacement-module'

The rule handles various import scenarios:

  • Named imports with aliases: import { restrictedImport as aliasName }
  • Mixed allowed/restricted imports: Will split into separate import statements
  • Default exports with named imports
  • Multiple restricted named imports
  • Merging with existing imports from replacement module

Examples of complex scenarios:

// Before
import { existingImport } from 'replacement-module';
import { restrictedImport } from 'restricted-module';

// After
import { existingImport, restrictedImport } from 'replacement-module';

// Before
import defaultExport, { restrictedImport, allowed } from 'restricted-module';

// After
import { restrictedImport } from 'replacement-module'
import defaultExport, { allowed } from 'restricted-module'

Rules

🔧 Automatically fixable by the --fix CLI option.

| Name | Description | 🔧 | | :----------------------------------------------- | :--------------------------------------- | :- | | restrict-import | Prevent the Import of a Specific Package | 🔧 |