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

@pro-vision/eslint-config-pv

v5.0.0

Published

pro!vision ESLint configuration. Can be adapted and adjusted in each project.

Readme

@pro-vision/eslint-config-pv

This package provides pro!vision's ESLint configuration as an extensible shared config.

Originally inspired by Airbnb

Rules mostly follow:

  • eslint's js.configs.recommended
  • typescript-eslint's strict-type-checked

[!IMPORTANT] Since version 5.0.0, only the eslint's flat config file is supported, for older .eslintrc config files please use this package @v4.0.0.

Installation

npm install --save-dev @pro-vision/eslint-config-pv
# in addition, for Typescript linting
npm install --save-dev typescript-eslint typescript
# in addition, to use with Prettier
npm install --save-dev eslint-plugin-prettier eslint-config-prettier prettier

Usage

Create an eslint.config.mjs (or eslint.config.cjs) file with necessary presets and customized rules. For example:

// eslint.config.mjs

import pvESLintTS from "@pro-vision/eslint-config-pv/typescript";
import pvESLintPrettier from "@pro-vision/eslint-config-pv/prettier";

export default [
  ...pvESLintTS,
  ...pvESLintPrettier,

  // modify rules if needed
  {
    rules: {
      "no-console": "off",
      "@typescript-eslint/unbound-method": "off",
      "import/order": [
        "error",
        {
          "newlines-between": "always",
          pathGroups: [
            {
              pattern: "{Helper,Components}/**",
              group: "internal",
            },
          ],
          pathGroupsExcludedImportTypes: [],
          groups: ["builtin", "external", "internal", ["index", "sibling", "parent"]],
        },
      ],
    }
  },
]

In detail for specific use cases:

Javascript files

// eslint.config.mjs

import pvESLintJS from "@pro-vision/eslint-config-pv/javascript";

export default [
  ...pvESLintJS,
]

Modifying rules

// eslint.config.mjs

import pvESLintJS from "@pro-vision/eslint-config-pv/javascript";

export default [
  ...pvESLintJS,

+  {
+    rules: {
+      "no-console": "off",
+      "import/order": [
+        "error",
+        {
+          "newlines-between": "always",
+          pathGroups: [
+            {
+              pattern: "{Helper,Components}/**",
+              group: "internal",
+            },
+          ],
+          pathGroupsExcludedImportTypes: [],
+          groups: ["builtin", "external", "internal", ["index", "sibling", "parent"]],
+        },
+      ],
+    }
+  }
]

With prettier

If you haven't installed prettier as your dependency already, then do

npm install --save-dev prettier

and update the eslint.config.mjs file

// eslint.config.mjs

  import pvESLintJS from "@pro-vision/eslint-config-pv/javascript";
+ import pvESLintPrettier from "@pro-vision/eslint-config-pv/prettier";

export default [
    ...pvESLintJS,
+   ...pvESLintPrettier,

    {
      rules: {
        ...
      }
    }
]

This will run eslint with your prettier config in addition to the previous eslint rules and report any formatting issues / auto fix them. Any @pro-vision/eslint-config-pv formatting rule (e.g. @stylistic/max-len) will automatically be ignored in favor of prettier configuration.

For Typescript files

Make sure you have already installed typescript as your dependency:

npm install --save-dev typescript

and update the eslint.config.mjs file using eslint-config-pv/typescript Instead of eslint-config-pv/javascript (It already contains all the rules in the /javascript config).

// eslint.config.mjs

- import pvESLintJS from "@pro-vision/eslint-config-pv/javascript";
+ import pvESLintTS from "@pro-vision/eslint-config-pv/typescript";
  import pvESLintPrettier from "@pro-vision/eslint-config-pv/prettier";

export default [
-  ...pvESLintJS,
+  ...pvESLintTS,
   ...pvESLintPrettier,

    {
      rules: {
        ...
      }
    }
]

@pro-vision/eslint-config-pv/typescript assumes your tsconfig.json file is in the same directory as where you call eslint. i.e. your projects root directory. But you can also specify this with:

// eslint.config.mjs

export default [
  ...
+  {
+    languageOptions: {
+      parserOptions: {
+        project: "./my-tsconfig.json",
+        tsconfigRootDir: "my-configs/",
+      },
+    },
+  },
]

For .js and .ts files in the same project

eslint-config-pv/typescript rules will apply only to .ts and .tsx files, and the other rules (eslint-config-pv/javascript and eslint-config-pv/prettier) will apply to both. The only thing that you have make sure of is that any rule customization for @typescript-eslint that needs type information (see the list of rules), are only applied to .ts(x) files. i.e.:

...
  {
    rules: {
      "no-console": "off",
-     "@typescript-eslint/no-misused-promises": ["error", { checksVoidReturn: false }],
    }
  },
+ {
+   files: ["**/*.ts", "**/*.tsx"],
+   rules: {
+     "@typescript-eslint/no-misused-promises": ["error", { checksVoidReturn: false }],
+   }
+ }