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-khvala-imports

v1.0.0

Published

ESLint plugins for imports

Downloads

1

Readme

ESLint Plugin: Import Path Restrictions

This ESLint plugin provides rules to enforce import path restrictions in your codebase. It helps maintain a clean and organized project structure by preventing imports from restricted directories.

Installation

npm install --save-dev @mwkt/eslint-plugin-imports

Usage

Add the plugin to your ESLint configuration:

{
  "plugins": ["imports"],
  "rules": {
    "imports/restrict-import-paths": "error"
  }
}

Rule: restrict-import-paths

This rule enforces restrictions on import paths in your codebase. It can be configured to:

  • Apply only to specific source folders
  • Restrict imports from certain directories

Options

The rule accepts an array of configuration objects, where each object can have the following properties:

  • sourceFolders (string[]): Array of folder paths where the rule should be applied. Default: ["/components/"]
  • restrictedFolders (string[]): Array of folder paths that should not be imported from. Default: ["/modules/"]

Example Configuration

{
  "rules": {
    "imports/restrict-import-paths": ["error", {
      "sourceFolders": ["client/lib/components"],
      "restrictedFolders": ["@lib/modules"]
    }]
  }
}

You can also provide multiple configuration objects to apply different restrictions to different source folders:

{
  "rules": {
    "imports/restrict-import-paths": ["error", 
      {
        "sourceFolders": ["client/lib/components"],
        "restrictedFolders": ["@lib/modules"]
      },
      {
        "sourceFolders": ["server/api"],
        "restrictedFolders": ["@lib/client"]
      }
    ]
  }
}

Examples

The rule will report errors for:

// ❌ Importing from a restricted folder
import { something } from '../modules/feature';

// ❌ Requiring from a restricted folder
const something = require('../modules/feature');

// ✅ Importing from allowed folders
import { something } from '../components/feature';

Features

  • Supports both ES6 imports and CommonJS require statements
  • Configurable source and restricted folders
  • Only applies to specified source files
  • Easy to integrate with existing ESLint configurations