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

@hughescr/eslint-plugin-module-boundaries

v1.0.0

Published

ESLint rules for module boundary enforcement: no cross-module @internal imports, no @internal re-exports in barrels, no star re-exports from non-barrel files

Readme

@hughescr/eslint-plugin-module-boundaries

ESLint rules for enforcing module boundary integrity in TypeScript projects using /** @internal */ JSDoc tags.

Requires TypeScript parser services (@typescript-eslint/parser with projectService).

Rules

| Rule | Description | |------|-------------| | no-cross-module-internal | Prevent importing @internal exports from a different architectural module | | no-internal-in-barrel | Prevent barrel index.ts files from re-exporting @internal exports | | no-star-export-from-non-barrel | Prevent barrel index.ts files from using export * from non-barrel files |

Requirements

  • ESLint v10+
  • TypeScript v5+
  • @typescript-eslint/parser with projectService enabled
  • Node.js v20+

Installation

bun add -D @hughescr/eslint-plugin-module-boundaries typescript @typescript-eslint/parser

Usage

Recommended config (flat config)

// eslint.config.mjs
import moduleBoundaries from '@hughescr/eslint-plugin-module-boundaries';
import { defineConfig } from 'eslint';

export default defineConfig([
  // Spread recommended — enables all three rules at 'error' severity
  ...Object.values(moduleBoundaries.configs.recommended),
]);

The recommended config enables all rules with 'error' severity. The no-cross-module-internal rule requires a modules option — see the full documentation for details.

With module boundaries defined

// eslint.config.mjs
import moduleBoundaries from '@hughescr/eslint-plugin-module-boundaries';
import { defineConfig } from 'eslint';
import typescriptParser from '@typescript-eslint/parser';

const modules = [
  { type: 'config',       pattern: 'src/config/**' },
  { type: 'utils',        pattern: 'src/utils/**' },
  { type: 'storage',      pattern: 'src/storage/**' },
  { type: 'services',     pattern: 'src/services/**' },
  { type: 'integrations', pattern: 'src/integrations/**' },
  { type: 'agent',        pattern: 'src/agent/**' },
  { type: 'app',          pattern: 'src/app/**' },
];

export default defineConfig([
  {
    files:           ['src/**/*.ts'],
    languageOptions: {
      parser:        typescriptParser,
      parserOptions: {
        projectService: true,
        tsconfigRootDir: import.meta.dirname,
      },
    },
    plugins: {
      '@hughescr/module-boundaries': moduleBoundaries,
    },
    rules: {
      '@hughescr/module-boundaries/no-cross-module-internal': ['error', { modules }],
      '@hughescr/module-boundaries/no-internal-in-barrel':          'error',
      '@hughescr/module-boundaries/no-star-export-from-non-barrel': 'error',
    },
  },
]);

How it works

All three rules use TypeScript's compiler API (ts.getJSDocTags()) to inspect @internal JSDoc tags on exported declarations — not fragile regex text scanning. This means aliased re-exports, default exports, namespaces, and enums are all handled correctly.

The rules require parserServices.program to be available, which means you must use @typescript-eslint/parser with projectService: true (or a project path).

Per-rule documentation

License

BSD-3-Clause — see LICENSE.md.