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

@vedapointe-shared/eslint-config

v2.0.0

Published

Shared ESLint flat config for VedaPointe TypeScript/Node.js/Express projects

Readme

@vedapointe-shared/eslint-config v2

Modern, opinionated ESLint flat config for VedaPointe TypeScript/Node.js/Express projects.

What's included

| Layer | Source | Purpose | | ---------- | ----------------------------------------------------------------- | ------------------------------------------------------ | | Base JS | @eslint/js recommended | Core JS error prevention | | TypeScript | typescript-eslint recommendedTypeChecked + stylisticTypeChecked | Type-aware linting + style consistency | | Node.js | eslint-plugin-n | Deprecated API detection, prefer modern APIs | | Security | eslint-plugin-security | Detect common security anti-patterns | | Testing | @vitest/eslint-plugin | Test best practices (Vitest/Jest-compatible) | | Formatting | eslint-config-prettier | Disables all formatting rules — let Prettier handle it |

Requirements

  • Node.js >= 18.18.0
  • ESLint >= 9.22.0
  • TypeScript >= 5.0.0

Installation

npm install --save-dev @vedapointe-shared/eslint-config eslint typescript

Usage

Create an eslint.config.mjs in your project root:

import vedapointe from "@vedapointe-shared/eslint-config";
import { defineConfig } from "eslint/config";

export default defineConfig(...vedapointe, {
  languageOptions: {
    parserOptions: {
      projectService: true,
      tsconfigRootDir: import.meta.dirname,
    },
  },
});

The tsconfigRootDir override is required so typescript-eslint can find your project's tsconfig.json.

With overrides

import vedapointe from "@vedapointe-shared/eslint-config";
import { defineConfig } from "eslint/config";

export default defineConfig(
  ...vedapointe,
  {
    languageOptions: {
      parserOptions: {
        projectService: true,
        tsconfigRootDir: import.meta.dirname,
      },
    },
  },
  {
    rules: {
      "no-console": "off",
      "@typescript-eslint/no-explicit-any": "off",
    },
  },
);

Custom ignores

import vedapointe from "@vedapointe-shared/eslint-config";
import { defineConfig } from "eslint/config";

export default defineConfig(
  { ignores: ["generated/**", "migrations/**"] },
  ...vedapointe,
  {
    languageOptions: {
      parserOptions: {
        projectService: true,
        tsconfigRootDir: import.meta.dirname,
      },
    },
  },
);

Design decisions

Lean on the presets. Rather than manually listing 100+ rules, we extend recommendedTypeChecked and stylisticTypeChecked from typescript-eslint. These are well-maintained, stable presets. Our custom layer only overrides where we have a specific reason to diverge.

Warnings vs errors. Rules are set to error when they catch definite bugs (floating promises, unused vars, exhaustive switches). Rules are set to warn when they surface code smells that may have legitimate exceptions (unnecessary conditions, unbound methods, require-await). This lets teams adopt gradually without blocking CI on day one.

Express-friendly. checksVoidReturn.arguments is disabled for no-misused-promises so async route handlers don't trigger false positives. ignoreStatic is enabled for unbound-method so static middleware references work.

Decorator/DI-friendly. no-extraneous-class is off to support DI containers like typedi where classes are used as service tokens.

Test files are relaxed. Type-safety rules are loosened in test files where mocking often requires any and assertions need flexibility.

Prettier handles formatting. Zero stylistic/formatting rules are enforced. Run Prettier separately.

Security as a safety net. Security rules that produce many false positives (detect-object-injection) are off. Others are warnings to surface issues without blocking.

Key rules added beyond the presets

| Rule | Severity | Why | | -------------------------------- | -------- | ---------------------------------------- | | consistent-type-imports | error | Cleaner builds, explicit type boundaries | | consistent-type-exports | error | Same as above for exports | | switch-exhaustiveness-check | error | Catch missing cases at compile time | | prefer-readonly | error | Immutability by default | | promise-function-async | error | Make async intent explicit | | return-await (in-try-catch) | warn | Catch unhandled rejections in try/catch | | no-unnecessary-type-parameters | warn | Avoid over-generic code | | n/no-deprecated-api | error | Stay off deprecated Node.js APIs | | n/prefer-promises/* | error | Use promise-based fs/dns APIs | | security/* | mixed | Baseline security hygiene |

Migrating from v1

v1 used the legacy .eslintrc format with eslint-plugin-jest. v2 is a complete rewrite:

  1. Remove old packages: @typescript-eslint/eslint-plugin, @typescript-eslint/parser, eslint-plugin-jest, eslint-plugin-prettier
  2. Update ESLint to v9+
  3. Delete .eslintrc / .eslintignore
  4. Create eslint.config.mjs as shown above
  5. Update your lint script: "lint": "eslint ."

License

ISC

Minor or major release

npm version minor   # or: npm version major
npm publish --access public