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

@nicksp/eslint-config

v1.5.4

Published

Nick's ESLint config

Readme

@nicksp/eslint-config

npm Node.js CI status

Shared ESLint config I use on my personal projects. Based on antfu's config.

Difference

  • Format with Prettier
  • Only the tools I use are supported
  • More stricter rules
  • Simpler setup

Highlights

  • Play well with TypeScript and Prettier
  • Target tools I use personally on the majority of the projects: React, Next, Astro and Vitest
  • Sort imports, package.json, tsconfig.json
  • ESLint flat config for better organization and composition
  • Respects .gitignore by default
  • Reasonable defaults, best practices, only one-line of config
  • Requires ESLint v9.5.0+

Setup

pnpm add -D eslint@latest @nicksp/eslint-config

Create eslint.config.mjs in your project root:

import { defineConfig } from '@nicksp/eslint-config'

export default defineConfig()

Add scripts for package.json:

{
  "scripts": {
    "lint": "eslint",
    "lint:fix": "eslint --fix",
    "format": "prettier --write \"**/*.{js,cjs,mjs,jsx,ts,tsx,astro,css,json,md}\""
  }
}

Configure VS Code for auto-fix on save in .vscode/settings.json:

{
  // Use the Prettier formatter
  "editor.defaultFormatter": "esbenp.prettier-vscode",
  "editor.formatOnSave": true,

  // Autosave files on focus change
  "files.autoSave": "onFocusChange",
  // Don’t autosave files with syntax errors
  "files.autoSaveWhenNoErrors": true,

  // Auto fix
  "editor.codeActionsOnSave": {
    "source.fixAll.eslint": "explicit",
    "source.organizeImports": "never"
  },

  // Silent the stylistic rules in your IDE, but still auto fix them
  "eslint.rules.customizations": [
    { "rule": "style/*", "severity": "off", "fixable": true },
    { "rule": "format/*", "severity": "off", "fixable": true },
    { "rule": "*-indent", "severity": "off", "fixable": true },
    { "rule": "*-spacing", "severity": "off", "fixable": true },
    { "rule": "*-spaces", "severity": "off", "fixable": true },
    { "rule": "*-order", "severity": "off", "fixable": true },
    { "rule": "*-dangle", "severity": "off", "fixable": true },
    { "rule": "*-newline", "severity": "off", "fixable": true },
    { "rule": "*quotes", "severity": "off", "fixable": true },
    { "rule": "*semi", "severity": "off", "fixable": true }
  ],

  // Enable eslint for all supported languages
  "eslint.validate": [
    "javascript",
    "javascriptreact",
    "typescript",
    "typescriptreact",
    "html",
    "markdown",
    "json",
    "json5",
    "jsonc",
    "yaml",
    "toml",
    "xml",
    "gql",
    "graphql",
    "astro",
    "css",
    "less",
    "scss",
    "pcss",
    "postcss"
  ]
}

Usage

// eslint.config.js
import { defineConfig } from '@nicksp/eslint-config'

export default defineConfig(
  {
    // Type of the project. 'lib' for libraries, the default is 'app'
    type: 'lib',

    // Formatting with Prettier is enabled by default, you can disable it
    prettier: false,

    // TypeScript is autodetected, you can also explicitly enable it
    typescript: true,

    // Disable jsx support
    jsx: false,

    // You can configure each integration individually as well
    yaml: {
      overrides: {
        // ...
      },
    },

    ignores: [
      '**/fixtures',
      // ...globs
    ]
  },

  // You can have multiple config overrides
  {
    files: ['**/*.ts'],
    rules: {},
  },
  {
    rules: {},
  },
)

// Advanced config
// See more at https://github.com/antfu/eslint-flat-config-utils
.prepend(
  // some configs before the main config
).removeRules('foo/bar')

Optional configs

These are optional configs for specific use cases.

Running npx eslint should prompt you to install the required dependencies, otherwise, you can install them manually.

// eslint.config.js
import { defineConfig } from '@nicksp/eslint-config'

export default defineConfig({
  // Enable React support
  react: true,

  // Enable Next.js support
  nextjs: true,

  // Enable Astro support
  astro: true,
})

Other Projects You Might Like

License

MIT License © 2025 Nick Plekhanov