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

@side-xp/biome-config

v1.2.1

Published

Shared Biome configuration for projects at Sideways Experiments

Readme

Sideways Experiments' Biome config

A few Biome config files shared across Sideways Experiments projects.

Usage

In your Node project, you must use Biome as your linting & formatting tool in order to use these configurations. Plus, you must install this package as dev dependency:

npm i -D @biomejs/biome @side-xp/biome-config

Create a biome.json file at the root of your project, and add an extends rule with the appropriate config file:

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

Our rules force using LF line-endings format. To make sure that your system doesn't conflict with this rule, you can add a .gitattributes at the root of your project, with the following content:

* text=auto eol=lf

For Node library projects

For Node library projects (that output a reusable package, not an app) you should also extend the biome.lib.json variant of our config:

{
  "extends": [
    "@side-xp/biome-config",
    "@side-xp/biome-config/biome.lib.json"
  ]
}

It enforces a few rules for libraries specifically, like considering an error to let console calls in the code unless they're used in tests.

For app projects

For Node app projects you should also extend the biome.app.json variant of our config:

{
  "extends": [
    "@side-xp/biome-config",
    "@side-xp/biome-config/biome.app.json"
  ]
}

It adds support for Tailwind directives like @theme.

Developer setup

git clone https://github.com/side-xp/biome-config
cd biome-config
npm install

The repository uses Husky to setup Git hooks:

  • Check if JSON files are valid (no parsing error) on commit
  • Enforce Conventional Commit notation in commit messages

Releases are automated with semantic-release in CI.


Crafted and maintained with love by Sideways Experiments

(c) 2022-2026 Sideways Experiments