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-debarrel

v0.5.2

Published

ESLint plugin to transform barrel imports into direct imports

Downloads

32

Readme

eslint-plugin-debarrel

An ESLint plugin to transform barrel imports into direct imports. For example:

import { Button, DatePicker } from "@cloudscape-design/components";

Will be transformed to:

import Button from "@cloudscape-design/components/button";
import DatePicker from "@cloudscape-design/components/date-picker";

Why?

Importing from barrel files (files that re-export multiple modules from a single entry point) negatively impacts build performance.

See:

Installation

npm install --save-dev eslint-plugin-debarrel

Usage

Flat config

In your eslint.config.mjs:

import eslintPluginDebarrel from "eslint-plugin-debarrel";

export default [
  // other config...
  {
    plugins: {
      debarrel: eslintPluginDebarrel,
    },
    rules: {
      "debarrel/debarrel": [
        "error",
        {
          patterns: [
            {
              barrel: "@cloudscape-design/components",
              transformPattern: "@cloudscape-design/components/{{importName}}",
              transformImportName: "kebab-case",
              namedExports: {
                suffixes: ["Props"],
              },
            },
          ],
        },
      ],
    },
  },
];

Legacy config

Add debarrel to the plugins section of your .eslintrc configuration file:

{
  "plugins": ["debarrel"]
}

Then configure the rule under the rules section:

{
  "rules": {
    "debarrel/debarrel": [
      "error",
      {
        "patterns": [
          {
            "barrel": "@cloudscape-design/components",
            "transformPattern": "@cloudscape-design/components/{{importName}}",
            "transformImportName": "lowercase",
            "namedExports": {
              "suffixes": ["Props"]
            }
          }
        ]
      }
    ]
  }
}

Rule configuration

For each barrel file you want to avoid, add an object to the patterns list with:

  • barrel: The import path of the barrel file
  • transformPattern: The path that each named import should be imported from as a default import instead, using {{importName}} as a placeholder
  • transformImportName (optional): Transform the original import name before using it in the transformPattern. The transform can be either a string-to-string function or one of the following: "lowercase" | "kebab-case" | "camelCase".
  • namedExports (optional): Configuration for handling imports that should be treated as named exports rather than default exports.
    • suffixes: Array of suffixes (e.g., ["Props", "Interface"]) that should be treated as named exports
    • customPattern (optional): Custom pattern for named exports, defaults to the same as transformPattern
    • transformImportName (optional): Custom function to transform the import name for named exports