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

@alborz-taiv/taiv-eslint-config

v1.2.0

Published

Taiv's shared ESLint configuration for consistent code formatting and linting across all projects.

Readme

@alborz-taiv/taiv-eslint-config

Taiv's shared ESLint configuration for consistent code quality and linting across all projects.

Installation

npm install --save-dev @alborz-taiv/taiv-eslint-config

Usage

This package uses ESLint's new flat config format. Import the config for your stack into an eslint.config.mjs file and extend as needed.

// eslint.config.mjs
import { reactConfig } from '@alborz-taiv/taiv-eslint-config';

export default [...reactConfig];

Available Configs

  • base - Base TypeScript configuration.
  • react - React configuration for web apps.
  • node - Node.js configuration for servers and backends.

Extending Configurations

You can extend any configuration by spreading it and adding your own rules:

// eslint.config.mjs
import { reactConfig } from '@alborz-taiv/taiv-eslint-config';

export default [
  ...reactConfig,
  {
    rules: {
      // Your custom rules here
      'no-console': 'off',
    },
  },
  {
    ignores: ['**/dist/**/*', '**/build/**/*'],
  },
];

Prettier Configuration

This package includes linting with Prettier. It will lint based off of our formatting rules:

{
  "tabWidth": 2,
  "printWidth": 120,
  "semi": true,
  "singleQuote": true,
  "arrowParens": "always",
  "trailingComma": "es5"
}

Scripts

Add these scripts to your package.json:

{
  "scripts": {
    "lint": "npx eslint .",
    "lint:fix": "npx eslint . --fix",
    "format": "npx prettier --write .",
    "format:check": "npx prettier --check .",
  }
}

Requirements

The following are required as dev dependencies for this package to be used.

  • Node.js 20+
  • ESLint 8.57.1+
  • TypeScript 4.5.3+
  • Prettier 3.6.2+

Plugins

This package uses the following eslint plugins/configs. Peers do NOT require these packages installed, but this package does rely on them.

  • eslint-config-prettier
  • eslint-import-resolver-typescript
  • eslint-plugin-import
  • eslint-plugin-react
  • typescript-eslint

Development

Local Testing

You can use npm link to test changes if you are developing within this repo.

# In the config package (this one)
npm link

# In your project, i.e., the web app
npm link @alborz-taiv/taiv-eslint-config

Publishing Updates

Do When you are ready to make changes, do a version bump and publish it. Then update any projects that use this package.

npm version patch  # or minor/major
npm publish