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

@rio-cloud/biome-config

v1.2.0

Published

A place for all our biome configs

Readme

biome-config

A place for all our biome configs - with the hope that it's only going to be one, actually

🐶 Disclaimers

Right now, only the frontend config exists, but it should work for non-frontend codebases just as well.

At the time of writing, this config is working with biome version 2.3.5 and most likely above.

⚠️ There have been some fluctuations regarding config structure in the past, though - so if you're running a newer biome version and experience weird behaviour, please get in touch.

🛠️ Installation

Add this npm package to your project's `devDependencies:

npm install --save-dev @rio-cloud/biome-config

Now, your minimal biome.json could look like this:

{
    "$schema": "node_modules/@biomejs/biome/configuration_schema.json",
    "extends": ["@rio-cloud/biome-config/frontend.json"],
    "root": true
}

By default, this config tells biome to integrate with your git repository so that it automatically ignores filed specified in your .gitignore file. You can, however, fine-tune what's covered by biome and what's not by setting the files.includes property.

Take a look at the the biome docs for reference.

💪 Using it

To make interacting with biome in the terminal easier, you can add some npm scripts to your package.json:

{
  /* ... */
  "scripts": {
    /* ... */
    "format-code": "biome format --write .",
    "lint": "biome lint .",
    "lint-fix": "biome lint --write .",
    "lint-fix-unsafe": "biome lint --write --unsafe .",
  }
  /* ... */
}

Depending on your IDE, we also recommend to activate biome and have it fix stuff on save automatically for you. There is a pretty good biome extension for intelliJ that allows these settings, for example:

intelliJ biome settings

❤️ Contributing

If you have a biome config that would like to see added here, please double-check if there's not already one that works for you. The frontend config should be sufficient for most (if not all) projects that are using TypeScript. And remember that you can always overrule or add settings to your local biome config without having to push those settings "upstream". After all, the configs in this repository are supposed to be a solid baseline for most of our projects - and hopefully, we can homogenize our code a bit.

If you see a config here and do want to change settings because you're sure that change needs to happen for everyone at RIO, feel free to open an issue on GitHub 😎