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

eslint-config-opencover

v3.0.7

Published

OpenCover specific linting rules for ESLint

Readme

eslint-config-opencover

ESLint flat config for OpenCover's TypeScript coding style.

Installation

pnpm add -D eslint-config-opencover eslint typescript

Usage

TypeScript project

// eslint.config.mjs
import opencover from 'eslint-config-opencover';

export default [...opencover];

React project

// eslint.config.mjs
import opencover from 'eslint-config-opencover';
import react from 'eslint-config-opencover/react';

export default [...opencover, ...react];

Next.js project

Install Next.js ESLint config alongside this package:

pnpm add -D eslint-config-next
// eslint.config.mjs
import opencover from 'eslint-config-opencover';
import nextVitals from 'eslint-config-next/core-web-vitals';
import nextTs from 'eslint-config-next/typescript';

export default [...nextVitals, ...nextTs, ...opencover];

OpenCover's config should come last so its rules take precedence.

Overriding rules

Each config object in the exported array has a name property for debugging (for example in ESLint's config inspector), but flat config overrides are matched by files/ignores, not by name. To override TypeScript-specific rules, add a later config object that matches the same files:

// eslint.config.mjs
import opencover from 'eslint-config-opencover';

export default [
  ...opencover,
  {
    files: ['**/*.{ts,tsx,mts,cts}'],
    rules: {
      '@typescript-eslint/explicit-function-return-type': 'off',
    },
  },
];

Later matching config objects override earlier ones for those files.

Available config names:

| Name | Description | | ---------------------- | ------------------------------------ | | opencover | Base rules (stylistic, imports, etc) | | opencover/gitignore | Ignores files from .gitignore | | opencover/typescript | TypeScript-specific rules | | opencover/test | Test file rules (vitest) | | opencover/react | React-specific TSX rules |