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-single-export

v1.1.2

Published

ESLint plugin to enforce a single export per file

Readme

eslint-plugin-single-export

An ESLint plugin that enforces a single export per file, promoting better module organization and clarity.

Installation

pnpm add -D eslint-plugin-single-export

Usage

ESLint 9 Flat Config (eslint.config.js)

import singleExport from 'eslint-plugin-single-export'

export default [
  {
    plugins: {
      'single-export': singleExport
    },
    rules: {
      'single-export/single-export': 'error'
    }
  }
]

Recommended Config

import singleExport from 'eslint-plugin-single-export'

export default [
  singleExport.configs.recommended
]

Rule: single-export

This rule enforces that each file should have exactly one export statement.

✅ Valid

// Single default export
export default function myFunction() {}

// Single named export
export const myConstant = 42

// Single export from another module
export { something } from './other-module'

// Single re-export all
export * from './other-module'

// CommonJS single export
module.exports = myFunction

❌ Invalid

// Multiple exports
export const a = 1
export const b = 2

// Mixed default and named exports
export default function myFunction() {}
export const myConstant = 42

// Multiple default exports
export default class A {}
export default class B {}

// Multiple CommonJS exports
module.exports = a
exports.b = 2

Why Single Exports?

  • Clarity: Each file has a single, clear purpose
  • Discoverability: Easier to understand what a module provides
  • Refactoring: Simpler to move and reorganize code
  • Tree Shaking: Better optimization in bundlers
  • Testing: Easier to mock and test individual modules

Development

# Install dependencies
pnpm install

# Run tests
pnpm test

# Run tests in watch mode
pnpm test:watch

# Lint the code
pnpm lint

# Release
pnpm release

License

MIT