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

@maxchang/biome-config

v0.1.8

Published

Max Chang's Biome config

Downloads

415

Readme

@maxchang/biome-config

npm version npm downloads license

Checked with Biome code style (Is that really a thing?)

Convention

  • Based on recommended rules from Biome
  • Using spaces as indentation.
  • Sorted imports, dangling commas
  • Single quotes, semicolons as needed

Features

  • Automatic import organization
  • Git integration, respects .gitignore by default
  • Customizable TypeScript, JavaScript, and JSON rules
  • Predefined ignore patterns for common files/directories
  • Partial support for .vue, .svelte, and .astro files

Usage

[!TIP] Not sure how to set up Biome? Take a look at the Getting Started guide from the official docs.

  1. Install Biome as a development dependency if you haven't already:

    # ✨ Auto-detect
    npx nypm install -D @biomejs/biome
    
    # npm
    npm install -D @biomejs/biome
    
    # yarn
    yarn add -D @biomejs/biome
    
    # pnpm
    pnpm add -D @biomejs/biome
    
    # bun
    bun install -D @biomejs/biome
    
    # deno
    deno install --dev npm:@biomejs/biome
  2. Install the config package as a development dependency:

    # ✨ Auto-detect
    npx nypm install -D @maxchang/biome-config
    
    # npm
    npm install -D @maxchang/biome-config
    
    # yarn
    yarn add -D @maxchang/biome-config
    
    # pnpm
    pnpm add -D @maxchang/biome-config
    
    # bun
    bun install -D @maxchang/biome-config
    
    # deno
    deno install --dev npm:@maxchang/biome-config
  3. Extend the config in your biome.json file:

    {
      "$schema": "https://biomejs.dev/schemas/2.3.13/schema.json",
      "extends": ["@maxchang/biome-config"],
    }
  4. Add the following scripts to your package.json:

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

Recipes

VS Code Settings

If you use VS Code, here is a reference settings.json, with automatic formatting on save and Biome as the default formatter for languages needed.

{
  "[typescript]": {
    "editor.defaultFormatter": "biomejs.biome"
  },
  "[javascript]": {
    "editor.defaultFormatter": "biomejs.biome"
  },
  "[javascriptreact]": {
    "editor.defaultFormatter": "biomejs.biome"
  },
  "[typescriptreact]": {
    "editor.defaultFormatter": "biomejs.biome"
  },
  "[json]": {
    "editor.defaultFormatter": "biomejs.biome"
  },
  "[jsonc]": {
    "editor.defaultFormatter": "biomejs.biome"
  },
  "[css]": {
    "editor.defaultFormatter": "biomejs.biome"
  },
  "editor.formatOnSave": true,
  "editor.codeActionsOnSave": {
    "source.fixAll.biome": "explicit",
    "source.organizeImports.biome": "explicit"
  }
}

Sort package.json keys

Since Biome has no plans to implement something like prettier-plugin-packagejson and currently lacks equivalent rules such as jsonc/sort-keys*, you can use sort-package-json as a workaround.

# npm
npx sort-package-json@latest

# pnpm
pnpm dlx sort-package-json@latest

# bun
bunx sort-package-json@latest

# deno
deno run -A npm:sort-package-json@latest

Git Hooks

I recommend using simple-git-hooks with lint-staged to run Biome checks before committing code.

Install the required dependencies:

# ✨ Auto-detect
npx nypm install -D simple-git-hooks lint-staged

# npm
npm install -D simple-git-hooks lint-staged

# yarn
yarn add -D simple-git-hooks lint-staged

# pnpm
pnpm add -D simple-git-hooks lint-staged

# bun
bun install -D simple-git-hooks lint-staged

# deno
deno install --dev npm:simple-git-hooks lint-staged

Add the following configuration to your package.json:

{
  "simple-git-hooks": {
    "pre-commit": "npx lint-staged"
  },
  "lint-staged": {
    "*": "biome check --no-errors-on-unmatched --files-ignore-unknown=true"
  }
}

then initialize the git hooks:

# npm
npx simple-git-hooks@latest

# pnpm
pnpm dlx simple-git-hooks@latest

# bun
bunx simple-git-hooks@latest

# deno
deno run -A npm:simple-git-hooks@latest

References


🤖 auto updated with automd