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

@accelint/biome-config

v1.1.1

Published

The shared Biome configuration used across Accelint projects.

Readme

@accelint/biome-config

Shared Biome configuration used across Accelint projects. Provides standardized linting, formatting, and analyzer settings for JavaScript and TypeScript codebases.

Features

  • Linter Configuration: Strict linting rules with cognitive complexity limits, naming conventions, and React hooks enforcement
  • Formatter Configuration: Consistent code formatting settings
  • Analyzer Configuration: Code analysis settings for better maintainability
  • Modular Design: Import only the configurations you need

Installation

# Using pnpm (recommended)
pnpm add -D @accelint/biome-config

# Using npm
npm install --save-dev @accelint/biome-config

# Using yarn
yarn add -D @accelint/biome-config

Usage

Complete Configuration

Create a biome.json file in your project root:

{
  "$schema": "https://biomejs.dev/schemas/2.3.8/schema.json",
  "extends": [
    "@accelint/biome-config/linter",
    "@accelint/biome-config/formatter",
    "@accelint/biome-config/analyzer"
  ]
}

Linter Only

For linting configuration only:

{
  "$schema": "https://biomejs.dev/schemas/2.3.8/schema.json",
  "extends": ["@accelint/biome-config/linter"]
}

Formatter Only

For formatting configuration only:

{
  "$schema": "https://biomejs.dev/schemas/2.3.8/schema.json",
  "extends": ["@accelint/biome-config/formatter"]
}

Analyzer Only

For code analysis configuration only:

{
  "$schema": "https://biomejs.dev/schemas/2.3.8/schema.json",
  "extends": ["@accelint/biome-config/analyzer"]
}

Configuration Details

Linter Rules

The linter configuration includes:

  • Complexity Rules

    • Maximum cognitive complexity: 15
    • Simplified logic expressions required
  • Correctness Rules

    • No undeclared variables
    • Exhaustive React hook dependencies (warning)
    • No unused imports or variables
    • React hooks must be at top level
  • Performance Rules

    • No re-export all statements
  • Style Rules

    • No negation in else clauses
    • Collapsed else-if statements
    • Block statements preferred
    • Shorthand array type syntax
    • No parameter reassignment
    • Naming conventions: camelCase/CONSTANT_CASE with ASCII-only
  • Suspicious Patterns

    • Array index as React key (warning)
    • No empty block statements
    • Async functions must use await
    • Explicit any types (warning)
    • No duplicate else-if conditions

Customization

You can override any rule in your project's biome.json:

{
  "extends": ["@accelint/biome-config/linter"],
  "linter": {
    "rules": {
      "complexity": {
        "noExcessiveCognitiveComplexity": {
          "options": {
            "maxAllowedComplexity": 20
          }
        }
      }
    }
  }
}

Scripts

Add these scripts to your package.json:

{
  "scripts": {
    "lint": "biome lint .",
    "lint:fix": "biome lint --write .",
    "format": "biome format --write .",
    "format:check": "biome format .",
    "check": "biome check --write ."
  }
}

Integration

VSCode

Install the Biome VSCode extension and add to your .vscode/settings.json:

{
  "editor.defaultFormatter": "biomejs.biome",
  "editor.formatOnSave": true,
  "editor.codeActionsOnSave": {
    "quickfix.biome": "explicit"
  }
}

CI/CD

Example GitHub Actions workflow:

- name: Run Biome
  run: |
    pnpm biome check .

License

Apache-2.0