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

@browsercore/dev

v0.2.0

Published

Shared build, lint, test, and coverage tooling for the @browsercore/* packages.

Readme

@browsercore/dev

npm version coverage license

Shared build, lint, test, and coverage tooling for every @browsercore/* package. One published package is the single source of truth; consumers extend it live via npm.

Install

npm install -D @browsercore/dev

Usage

tsconfig

{
  "extends": "@browsercore/dev/tsconfig.base.json",
  "compilerOptions": { "rootDir": "src", "outDir": "dist" },
  "include": ["src/**/*.ts"],
  "exclude": ["node_modules", "dist", "tests"]
}

For builds that emit declarations, extend @browsercore/dev/tsconfig.build.base.json instead (layers declaration, declarationMap, sourceMap on top of the base).

vitest

import { definePackageConfig } from "@browsercore/dev/vitest";

export default definePackageConfig({ name: "<pkg>" });

definePackageConfig wires in the shared reporters (text, html, json-summary), v8 coverage over src/**/*.ts, and 30s test/hook timeouts. The html + json-summary artifacts are what the coverage report reads. Pass { include, coverage } to override test globs or append coverage excludes.

oxlint

oxlint's JSON extends only resolves relative file paths (not node_modules), so the base is consumed via a TS import:

import { defineConfig } from "oxlint";
import base from "@browsercore/dev/oxlint";

export default defineConfig({ extends: [base] });

Type-aware linting (--type-aware) requires oxlint-tsgolint in the consumer's devDependencies.

coverage-md

After running vitest with coverage, generate a COVERAGE.md report + shields.io badge:

npx vitest run --coverage
npx coverage-md

The bin reads coverage/coverage-summary.json (written by the json-summary reporter) and writes COVERAGE.md and coverage/badge.json to the package root.

Scripts

| Command | Runs | | --- | --- | | npm run typecheck | tsc -p tsconfig.json --noEmit | | npm run lint | oxlint --type-aware src/ | | npm test | vitest run | | npm run build | tsc -p tsconfig.build.json |

Coverage report

To produce a coverage report:

npx vitest run --coverage
node scripts/coverage-md.mjs    # writes COVERAGE.md + coverage/badge.json

Provider is @vitest/coverage-v8. The report is generated from coverage/coverage-summary.json.

License

MIT