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

@openregion/biome-config

v1.0.0

Published

Open Region shared Biome config

Readme

Biome shared config

Open Region shared configuration for Biome.

This package replaces @openregion/eslint-config and @openregion/prettier-config for projects that are ready to move to Biome. It is a new recommended baseline, not a rule-for-rule migration of the previous ESLint, Airbnb, React, TypeScript ESLint, JSX accessibility, or Prettier settings.

Installation

npm install --save-dev @biomejs/biome @openregion/biome-config

Usage

Create biome.json in the project root:

{
  "extends": ["@openregion/biome-config"]
}

Add scripts to the consumer project's package.json:

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

Included baseline

  • Biome formatter.
  • Biome recommended linter rules.
  • Import organization through Biome assist actions.
  • Git ignore integration.
  • Conservative Open Region defaults for JavaScript and TypeScript projects.

Migration from Open Region ESLint and Prettier configs

Remove the old packages:

npm uninstall @openregion/eslint-config @openregion/prettier-config eslint prettier

Install Biome and the shared config:

npm install --save-dev @biomejs/biome @openregion/biome-config

Add biome.json:

{
  "extends": ["@openregion/biome-config"]
}

When the project is ready to apply formatting and safe fixes, run:

npx biome check --write .

Review the resulting diff before committing. Biome formatter output can differ from Prettier, and recommended lint rules can surface findings that were not covered by the old shared configs.

Local package checks

npm run check
npm run ci
npm run pack:dry-run