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

@kcconfigs/biome

v3.0.0

Published

Shared biome configuration

Readme

@kcconfigs/biome

Shared Biome formatter, linter, and assist settings.

Prerequisites

  • Biome: 2.0.0 or higher (as peer dependency)

Installation

pnpm add --save-dev @biomejs/biome @kcconfigs/biome

Usage

Add a biome.json (or biome.jsonc) that extends the default preset:

{
  "$schema": "https://biomejs.dev/schemas/2.5.15/schema.json",
  "extends": ["@kcconfigs/biome"]
}

Integrate with vscode

I recommended to add following to .vscode/settings.json.

{
  "editor.codeActionsOnSave": {
    "source.fixAll.biome": "explicit"
  }
}

Presets

| Name | Description | | ----------------------- | --------------------------------------------------------------------------------------------- | | @kcconfigs/biome | Default preset. Extends base and adds file includes/excludes plus useEditorconfig | | @kcconfigs/biome/base | Bare preset with formatter, linter, and assist rules only, without workspace-specific filters |

The default preset excludes generated artifacts such as dist, .vitest, lock files, *.tsbuildinfo, and release-please manifests. See default.json for the full list.

Use base when you need to own the include/exclude patterns yourself.

Formatter defaults

Inherited from base.json:

  • Indent style: tab
  • Indent width: 2
  • Line width: 120
  • Line ending: LF
  • VCS integration: enabled, uses .gitignore, default branch main

The default preset also sets formatter.useEditorconfig to true, so an .editorconfig in your repository takes precedence over the values above.

Test file relaxations

The default preset relaxes a few rules for **/*.test.*, **/*.spec.*, and **/__mocks__/**:

  • complexity/useLiteralKeys: off
  • suspicious/noExplicitAny: off
  • style/noNonNullAssertion: off

Example

Base preset with custom includes and a rule override:

{
  "$schema": "https://biomejs.dev/schemas/2.5.15/schema.json",
  "extends": ["@kcconfigs/biome/base"],
  "files": { "includes": ["src/**/*.ts", "tests/**/*.ts"] },
  "linter": {
    "rules": {
      "complexity": {
        "noUselessSwitchCase": "warn"
      }
    }
  }
}