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

@nesvet/biome-config

v2.0.5

Published

Shareable Biome config: formatter, linter, import organization, type-aware rules

Readme

@nesvet/biome-config

CI npm

My Biome config. Tabs, double quotes, type over interface, no trailing commas, almost no wrapping (lineWidth: 320).

Needs @biomejs/biome ^2.5.0.

bun add -d @nesvet/biome-config @biomejs/biome
{
	"$schema": "./node_modules/@biomejs/biome/configuration_schema.json",
	"extends": ["@nesvet/biome-config/node"]
}

/node requires the node: import protocol. Drop /node if you don't want that.

Bun is a known global. Imports are grouped (bun/node, packages, aliases, paths, CSS) with no blank lines between groups. Floating Promises are errors. CommonJS is an error. JSX files get React and a11y rules even if react is not in package.json.

Do not append /biome.json to extends.

Monorepo package:

{
	"extends": "//"
}

Override anything in your own biome.json. Files matching *.config.ts / *.config.js (and .mjs, .cjs, .mts, .cts) may use a default export: noDefaultExport is off there so tool configs still format and lint. Object and type property names may be CONSTANT_CASE (POSIX env keys) and may start with _ or $. A const may be PascalCase; a let may not.

Contributing

CONTRIBUTING.md

License

MIT