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

@stkd/biome

v1.0.2

Published

Shared Biome configuration defaults for STKD projects

Readme

@stkd/biome

Shared Biome configuration defaults for STKD projects.

Installation

npm install @stkd/biome --save-dev

Adding Biome to a New Repository

  1. Install dependencies:

    npm install @stkd/biome @biomejs/biome --save-dev
  2. Create biome.json in the project root:

    {
      "$schema": "https://biomejs.dev/schemas/2.3.10/schema.json",
      "extends": ["@stkd/biome"],
      "files": {
        "includes": ["src/**/*.{js,jsx,ts,tsx}"]
      }
    }
  3. Add scripts to package.json:

    "scripts": {
      "format": "biome format --write",
      "format-lint": "biome check --write",
      "lint": "biome lint --write"
    }
  4. Run formatting:

    npm run format-lint

Usage

In your project's biome.json, extend this base configuration:

{
  "$schema": "https://biomejs.dev/schemas/2.3.10/schema.json",
  "extends": ["./node_modules/@stkd/biome/biome.json"],
  "files": {
    "includes": ["src/**/*.{js,jsx,ts,tsx}"]
  }
}

Base Configuration

The base config provides:

Formatter

  • Indent style: tabs
  • Line width: 120 characters
  • Quote style: single quotes (JavaScript and CSS)

Linter Rules

  • recommended: enabled
  • noUnusedImports: error
  • noUnusedVariables: error
  • useParseIntRadix: off
  • useNodejsImportProtocol: off
  • noDoubleEquals: off
  • noGlobalIsNan: off
  • useLiteralKeys: off
  • useOptionalChain: off
  • useIterableCallbackReturn: off
  • noDocumentCookie: info
  • noDuplicateProperties: error

CSS Support

  • Tailwind directives parsing enabled
  • noUnknownAtRules ignores tailwind and apply

Assists

  • organizeImports: on
  • useSortedKeys: on
  • useSortedProperties: on

Vue Support

Vue files have relaxed rules (no unused import/variable warnings) since SFC compilers handle these.

Repository Customization

Each repository should override:

files.includes

Define which files Biome should process:

"files": {
  "includes": ["src/**/*.{js,jsx,ts,tsx}"]
}

Releasing

This package uses GitHub Actions with npm Trusted Publishing for secure, secret-free publishing.

| Workflow | Purpose | | -------- | ---------------------------- | | Release | Patch, minor, or major bump |

To release:

  1. Go to the Actions tab in the GitHub repository
  2. Click Release
  3. Choose patch, minor, or major
  4. Click Run workflow
  5. The version will be bumped, published to npm, and changes pushed automatically

Trusted Publishing note:

  • Configure npm to trust the exact workflow file you run: release.yml
  • Keep Trusted Publishing pointed at this single workflow file

Schema Version

Base config uses: 2.3.10

When upgrading, update the $schema in both this base config and all projects that extend it.