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

@aprx/biome-config

v0.4.1

Published

An opinionated Biome configuration

Readme

@aprx/biome-config

Setup

  • Install the package
npm install --dev @aprx/biome-config @biomejs/biome
  • Choose which preset you need from the list below and add it to your biome.json
{
  "extends": ["@aprx/biome-config/react", "@aprx/biome-config/testing"]
}

Presets

Hierarchy

Presets are organized in layers. Each preset inherits all rules from its parent:

base                  Universal JS/TS rules (formatter, linter, assist)
├── dom               + browser/DOM rules (a11y, security)
│   ├── react         + React-specific rules
│   │   └── nextjs    + Next.js-specific rules
│   └── vue           + Vue-specific rules
└── lib               + Node.js-specific rules

testing               Composable with any preset above

Reference

| Preset | Use case | |----------------------------------|--------------------------------------------| | @aprx/biome-config | Base rules only (e.g. universal library) | | @aprx/biome-config/dom | Browser/DOM application without framework | | @aprx/biome-config/lib | Node.js library or backend service | | @aprx/biome-config/react | React application (includes dom) | | @aprx/biome-config/nextjs | Next.js application (includes react) | | @aprx/biome-config/vue | Vue application (includes dom) | | @aprx/biome-config/testing | Test files (combine with any preset above) |

Examples

React application with tests:

{
  "extends": ["@aprx/biome-config/react", "@aprx/biome-config/testing"]
}

Node.js backend with tests:

{
  "extends": ["@aprx/biome-config/lib", "@aprx/biome-config/testing"]
}

Vanilla browser application:

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

Monorepo usage

In a monorepo, create a biome.json at the root and per-package configs that extend it using the "//" syntax:

monorepo/
├── biome.json                  Root config
├── packages/
│   ├── ui/
│   │   └── biome.json          Extends root + react preset
│   ├── api/
│   │   └── biome.json          Extends root + lib preset
│   └── shared/
│       └── biome.json          Extends root only

Root biome.json:

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

Package packages/ui/biome.json:

{
  "extends": ["//", "@aprx/biome-config/react", "@aprx/biome-config/testing"]
}

The "//" syntax tells Biome to inherit from the root configuration regardless of the package location. See the Biome monorepo guide for more details.

VS Code integration

Install the Biome extension (biomejs.biome), then add the following to your .vscode/settings.json:

{
  "editor.defaultFormatter": "biomejs.biome",
  "editor.formatOnSave": true,
  "editor.codeActionsOnSave": {
    "source.fixAll.biome": "explicit",
    "source.organizeImports.biome": "explicit"
  }
}

This enables format on save, auto-fix of lint issues, and import sorting.

Resources

License

MIT