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

v1.1.0

Published

Extended set of import related ESLint rules.

Readme

eslint-plugin-import-extended

Rules

no-internal-from-external-modules

This rule prevents external modules and files from accessing a module's internals, while allowing the module itself to reference its own internals. Modules can still accessed via their index files, establishing a pattern of public vs private interfaces.

Options

| Option | type | description | Ex | | ---------- | --------------------------------------- | --------------------------------------------------------- | --------------------------------------------- | | moduleRoot | array of strings (path or glob pattern) | Sets the top level folder where a module may be accessed. | [**/packages/*] or [src/modules/myModule] |

Examples

Given the following folder structure:

my-project
├── packages
│   └── package-one
│       └── index.ts
│       └── internal-file-one.ts
│   └── package-two
│       └── index.ts
│       └── internal-file-two.ts
└── entry.js

And the .eslintrc file:

{
  ...
  "rules": {
    "import-extended/no-internal-from-external-modules": [ "error", {
      "moduleRoot": ["**/packages/*"],
    } ]
  }
}

The following patterns are considered problems:

// in my-project/entry.ts
import {settings} from "my-project/packages/package-one/internal-file-one";
import reducer from "my-project/packages/package-two/internal-file-two";
export * from "/packages/package-two/internal-file-two";
// in my-project/packages/package-two/index.ts
import {settings} from "my-project/packages/package-one/internal-file-one";

The following patterns are NOT considered problems:

// in my-project/packages/package-two/index.ts
import reducer from "my-project/packages/package-two/internal-file-two";
// in my-project/packages/package-one/index.ts
import { settings } from "my-project/packages/package-two;
import { settings } from "my-project/packages/package-two/index.ts;
// in my-project/entry.ts
import * from "my-project/packages/package-one;

Contributing

This projects uses Yarn Modern and Corepack. To install the project for development, you must first make sure corepack is enabled, run:

corepack enable

You can then run yarn && yarn bootstrap. The bootstrap command will configure git hooks.