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-import-encapsulation

v1.0.5

Published

This plugin provides rules to enforce the best import path for encapsulation

Readme

📦 Installation

$ npm install --save-dev eslint-plugin-import-encapsulation
$ yarn add -D eslint-plugin-import-encapsulation

📔 Usage

{
  ...
  "plugins": ["import-encapsulation"],


  ...
}

Usecase

It helps to specify the path for directory-by-directory encapsulation using eslint-plugin-import-access, etc.
For example, by referring to a file in the encapsulation by a relative path, it is made explicit that the referenced file is an element of the encapsulated module. It is also smart because the references will not be broken if the module is moved to a different directory.
On the other hand, for files outside the module, we use absolute paths to make it explicit that we are calling an external file.
In this way, encapsulation can be of high quality.

📖 Rules

encapsulation

This rule checks the proximity between the import path and the current file.

If the proximity is greater than the specified value, it will be an error.

Options

  • maxDepth (default: 3): The maximum depth of import path deps.
  • rootDir (default: ""): The root directory of the project. (e.g. src)
  • prefix (default: ""): The prefix of the import path. (e.g. @)
  • ignoreTopLevel (default: 2): The number of the upper level hierarchy for which absolute import is allowed.

Example1

{
  ...
  "rules": [
    "encapsulation-import/encapsulation": ["error", { "maxDepth": 3 }]
  ]
  ...
}
// This is a file in src/foo/bar/sub/index.js

// ✅ Good
import { foo } from './foo';
import { bar } from './bar';

// ✅ Good
import { foo } from '../foo';
import { bar } from './foo/bar';

// ✅ Good
import { foo } from '../../foo';
import { bar } from './foo/bar/baz';

// ❌ Bad
import { foo } from '../../../foo';
import { bar } from './foo/bar/baz/bar';

// ❌ Bad
import { foo } from '../../../foo';
import { bar } from '../../../foo/bar';

// ❌ Bad
import { foo } from '../../../foo';
import { bar } from '../../../foo/bar/baz';

// ✅ Good
import { foo } from 'src/foo';
import { bar } from 'src/bar';

// ✅ Good
import { foo } from 'src/foo';
import { bar } from 'src/foo/bar';

// ❌ Bad
import { bar } from 'src/foo/bar/sub/bar';
import { foo } from 'src/foo/bar/sub/foo';


// ❌ Bad
import { bar } from 'src/foo/bar/sub/bar';
import { foo } from 'src/foo/bar/sub/foo/baz';

// ❌ Bad
import { bar } from 'src/foo/bar/sub/bar';
import { foo } from 'src/foo/bar/foo/baz/boo';

Example2

{
  ...
  "rules": [
    "encapsulation-import/encapsulation": ["error", { "ignoreTopLevel": 1, "rootDir": "src" }]
  ]
  ...
}
// This is a file in src/foo/bar/sub/index.js

// ✅ Good
import { foo } from 'foo';
import { bar } from 'bar';

// ❌ Bad
import { bar } from 'foo/bar';