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

@neolith/eslint-config

v1.0.39

Published

Shared ESLint configurations for Genesis monorepo packages

Readme

@genesis/eslint-config

Shared ESLint configurations for the Genesis monorepo.

Installation

pnpm add -D @genesis/eslint-config eslint typescript

Available Configurations

Base Configuration

The base configuration provides TypeScript support with strict type checking rules.

// .eslintrc.js
module.exports = {
  extends: ['@genesis/eslint-config/base'],
  parserOptions: {
    project: './tsconfig.json',
  },
};

Next.js Configuration

Extended configuration for Next.js applications with React support.

// .eslintrc.js
module.exports = {
  extends: ['@genesis/eslint-config/next'],
  parserOptions: {
    project: './tsconfig.json',
  },
};

Library Configuration

Stricter configuration for shared packages with documentation requirements.

// .eslintrc.js
module.exports = {
  extends: ['@genesis/eslint-config/library'],
  parserOptions: {
    project: './tsconfig.json',
  },
};

Configuration Features

Base (@genesis/eslint-config/base)

  • TypeScript strict type checking
  • Explicit function return types
  • No explicit any types
  • Strict boolean expressions
  • Promise handling rules
  • Prettier compatibility

Next.js (@genesis/eslint-config/next)

  • All base rules (with some relaxed for app code)
  • Next.js core web vitals
  • React and React Hooks rules
  • Automatic detection of React version
  • Special handling for Next.js file conventions (pages, layouts, etc.)

Library (@genesis/eslint-config/library)

  • All base rules (stricter)
  • JSDoc documentation requirements for exported functions
  • Consistent type imports
  • No console statements
  • Import organization

Customization

You can override any rules in your project's ESLint configuration:

// .eslintrc.js
module.exports = {
  extends: ['@genesis/eslint-config/base'],
  parserOptions: {
    project: './tsconfig.json',
  },
  rules: {
    // Override specific rules
    '@typescript-eslint/explicit-function-return-type': 'off',
  },
};

TypeScript Configuration

Ensure your tsconfig.json includes the files you want to lint:

{
  "compilerOptions": {
    "strict": true
  },
  "include": ["src/**/*", ".eslintrc.js"]
}

Integration with Prettier

All configurations include eslint-config-prettier to disable formatting rules that conflict with Prettier. Make sure to run Prettier separately for formatting.