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

@thunderid/eslint-plugin

v1.0.1

Published

ESLint plugin for ThunderID projects

Readme

@thunderid/eslint-plugin

ESLint plugin for ⚡️ ThunderID projects with custom rules and configurations.

Installation

npm install --save-dev @thunderid/eslint-plugin eslint
# or
pnpm add -D @thunderid/eslint-plugin eslint

Usage

ESLint Flat Config (ESLint 9+)

// eslint.config.js
import thunderIdPlugin from '@thunderid/eslint-plugin';

export default [
  {
    plugins: {
      '@thunderid': thunderIdPlugin,
    },
    rules: {
      '@thunderid/copyright-header': 'error',
      '@thunderid/no-internal-imports': 'error',
      '@thunderid/prefer-system-utils': 'warn',
    },
  },
  // Or use a predefined config
  ...thunderIdPlugin.configs.recommended,
];

Predefined Configurations

recommended

General rules for all frontend projects:

  • @thunderid/copyright-header: Enforces the Apache 2.0 SPDX copyright header
  • @thunderid/no-internal-imports: Prevents importing from internal paths

typescript

Rules for TypeScript projects:

  • Extends @typescript-eslint/recommended
  • @thunderid/copyright-header: Enforces copyright headers
  • @thunderid/no-internal-imports: Prevents internal imports

react

Rules for React projects:

  • Extends plugin:react/recommended and plugin:react-hooks/recommended
  • @thunderid/copyright-header: Enforces copyright headers
  • @thunderid/no-internal-imports: Prevents internal imports
  • React-specific rules and settings

next

Rules for Next.js projects:

  • Extends next/core-web-vitals
  • @thunderid/copyright-header: Enforces copyright headers
  • @thunderid/no-internal-imports: Prevents internal imports

Rules for TypeScript frontend projects:

  • @thunderid/copyright-header: Enforces copyright headers
  • @thunderid/no-internal-imports: Prevents internal imports

Rules

@thunderid/copyright-header

Enforces the presence of the Apache 2.0 SPDX copyright header in all source files.

Options:

  • excludePatterns: Array of regex patterns for files to exclude
  • template: Custom copyright header template

Examples:

// ❌ Incorrect - missing header
export const foo = 'bar';

// ✅ Correct - has proper header
// Copyright 2025 The ThunderID Authors
// SPDX-License-Identifier: Apache-2.0
export const foo = 'bar';

@thunderid/no-internal-imports

Prevents importing from internal directories of other modules to maintain proper module boundaries.

Options:

  • allowedPatterns: Array of regex patterns for allowed internal imports
  • forbiddenPatterns: Array of regex patterns for forbidden imports

Examples:

// ❌ Incorrect - importing from internal path
import {secret} from 'package/internal/secret';
import {build} from 'package/lib/build';

// ✅ Correct - using public API
import {publicApi} from 'package';
import {helper} from './helper'; // relative imports are OK

Development

Building

pnpm build

Testing

pnpm test

Linting

pnpm lint

License

Apache 2.0 - see LICENSE file for details.