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 ๐Ÿ™

ยฉ 2025 โ€“ย Pkg Stats / Ryan Hefner

@hyperse/eslint-config-hyperse

v1.5.0

Published

๐Ÿ›  These are settings for TypeScript / ESLint / Prettier in a project

Readme

@hyperse/eslint-config-hyperse

๐Ÿ›  A comprehensive ESLint and Prettier configuration for TypeScript projects, with support for monorepos and ESM. Optimized for Next.js and React applications. โšก๏ธ

Features

  • ๐ŸŽฏ TypeScript & JavaScript Linting: Latest standards-based linting for both TypeScript and JavaScript
  • ๐Ÿ”ง Multiple Config Presets: Ready-to-use configurations for react, hooks, next, and more
  • ๐Ÿ“ Shared TypeScript Config: Pre-configured tsconfig.json for consistent TypeScript settings
  • ๐Ÿ’… Prettier Integration: Automatic code formatting with sensible defaults
  • โ™ฟ๏ธ Accessibility: Built-in rules for JSX accessibility
  • ๐Ÿ“ฆ Monorepo Support: Optimized for monorepo setups
  • ๐Ÿ”„ Module Support: Full compatibility with both ESM and CommonJS
  • ๐ŸŽจ Tailwind CSS: Built-in support for Tailwind CSS class sorting
  • ๐Ÿ” SonarJS: Optional integration for code quality rules

Installation & Configuration

Basic Setup

  1. Initialize your project (if needed):

    npm init
  2. Install the ESLint config:

    npm i -D @hyperse/eslint-config-hyperse
  3. Create ESLint configuration:

    • Create eslint.config.js (or eslint.config.mjs for CommonJS) in your project root
    • Add the base configuration:
    import { base, defineConfig } from '@hyperse/eslint-config-hyperse';
    
    export default defineConfig([
      ...base,
      {
        rules: {
          '@typescript-eslint/no-explicit-any': 'off',
        },
      },
    ]);

TypeScript Configuration

Base Configuration (tsconfig.json)

{
  "$schema": "https://json.schemastore.org/tsconfig",
  "extends": "@hyperse/eslint-config-hyperse/tsconfig.base.json",
  "compilerOptions": {
    "baseUrl": "./",
    "rootDir": ".",
    "outDir": "dist",
    "types": ["vitest/globals"],
    "paths": {}
  },
  "include": ["next-env.d.ts", "**/*.ts", "**/*.tsx"]
}

Build Configuration (tsconfig.build.json)

{
  "extends": "./tsconfig.json",
  "compilerOptions": {
    "outDir": "./dist",
    "rootDir": "./src",
    "baseUrl": "./",
    "incremental": false,
    "paths": {}
  },
  "exclude": ["**/*.stories.tsx", "**/*.stories.mdx", ".storybook/**", "dist"]
}

Available Scripts

Add to your package.json:

{
  "scripts": {
    "lint": "tsc --noEmit && eslint .",
    "lint:fix": "npm run lint -- --fix"
  }
}

Or for JavaScript-only projects:

{
  "scripts": {
    "lint": "eslint .",
    "lint:fix": "npm run lint -- --fix"
  }
}

Framework-Specific Configurations

Next.js

import { defineConfig, nextjs } from '@hyperse/eslint-config-hyperse';

export default defineConfig([
  ...nextjs,
  {
    rules: {
      '@typescript-eslint/no-explicit-any': 'off',
    },
  },
]);

React.js (without Next.js)

import { defineConfig, reactjs } from '@hyperse/eslint-config-hyperse';

export default defineConfig([
  ...reactjs,
  {
    rules: {
      '@typescript-eslint/no-explicit-any': 'off',
    },
  },
]);

SonarJS Integration

import { defineConfig, sonarjs } from '@hyperse/eslint-config-hyperse';

export default defineConfig([
  ...sonarjs,
  {
    rules: {
      'sonarjs/fixme-tag': 'warn',
      'sonarjs/todo-tag': 'warn',
    },
  },
]);

VS Code Integration

  1. Install the ESLint extension

  2. Configure VS Code settings (.vscode/settings.json):

{
  "editor.formatOnSave": true,
  "editor.defaultFormatter": "dbaeumer.vscode-eslint",
  "editor.codeActionsOnSave": {
    "source.fixAll": "explicit",
    "source.organizeImports": "never"
  },
  "[jsonc]": { "editor.formatOnSave": false },
  "[json]": { "editor.formatOnSave": false },
  "eslint.workingDirectories": [
    "./apps/docs",
    "./apps/web",
    "./packages/core",
    "./packages/utils"
  ],
  "files.associations": {
    "*.css": "tailwindcss"
  },
  "editor.quickSuggestions": {
    "strings": "on"
  },
  "tailwindCSS.classFunctions": ["tw", "clsx", "twMerge", "extendVariants"],
  "tailwindCSS.classAttributes": ["className", "classNames"],
  "tailwindCSS.experimental.configFile": {
    "apps/web/src/app/globals.css": "apps/web/src/**",
    "apps/docs/src/app/globals.css": "apps/docs/src/**"
  }
}

Additional Configuration

Prettier Configuration

Create prettier.config.mjs:

/**
 * @see https://prettier.io/docs/configuration
 * @type {import("prettier").Config}
 */
const config = {
  semi: true,
  singleQuote: true,
  trailingComma: 'es5',
  // ... your custom config
};

export default config;

Tailwind CSS Integration

  1. Add type support in types.d/global.d.ts:
import 'prettier';
import 'prettier-plugin-tailwindcss';
  1. Configure Tailwind in prettier.config.mjs:
const config = {
  tailwindStylesheet: './src/app/globals.css',
  tailwindFunctions: ['tw', 'clsx', 'twMerge', 'extendVariants'],
  tailwindAttributes: ['className', 'classNames'],
};

export default config;

Important Notes

  • TypeScript settings:
    • isolatedModules: true (default)
    • verbatimModuleSyntax: true (default)
  • JSON/JSONC files: VS Code formatting is disabled by default
  • React ESLint rules: See source code

Performance Considerations

The following ESLint rules may impact performance during linting/formatting:

  • prettier/prettier: Can be slow on large files due to full reformatting
  • @typescript-eslint/no-deprecated: Requires type information which increases checking time
  • sonarjs/arguments-order: Complex analysis of function argument usage patterns

Consider selectively disabling these rules for specific files if performance becomes an issue.