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

@webority/biome-config

v0.9.11

Published

Shared Biome lint + format policy for Webority frontend products. Extend it from a product biome.json so every repo inherits one fleet-decided ruleset, bumped by version — no per-repo drift.

Readme

@webority/biome-config

The single source of truth for Biome lint + format policy across Webority frontend products. Extend it from a product's biome.json so every repo inherits the same shared ruleset — and a policy change is one version bump, not an N-way copy that drifts. Same model as the shared @webority/theme + @webority/ui-react.

Use

npm install -D --save-exact @webority/biome-config
npm install -D @biomejs/biome

--save-exact is deliberate — pin @webority/* to an exact version, never ^, so a policy change arrives when you bump it rather than on someone's next npm install.

Then a product's biome.json extends this base and adds only its own repo-specific bits — vcs.root and files.includes:

{
  "$schema": "https://biomejs.dev/schemas/2.5.5/schema.json",
  "extends": ["@webority/biome-config/biome.jsonc"],
  "vcs": { "enabled": true, "clientKind": "git", "useIgnoreFile": true, "root": ".." },
  "files": {
    "ignoreUnknown": true,
    "includes": ["**", "!!**/dist", "!!**/build", "!!**/node_modules", "!**/src/appsettings.Compiled.json", "!**/public/version.json"]
  }
}

Never set formatter.lineEnding in a product. It is lf here, for every consuming repo, matching their .gitattributes (* text=auto eol=lf) and .editorconfig (end_of_line = lf). This config sets useEditorconfig: false, so the value above is the only place the line ending is stated — a local override is the deviation, and a stale one fails every file in the repo at once, drowning any real violation (one repo's leftover "lineEnding": "crlf" failed 198 of its 203 files; removing it left 1).

What's decided here (once, for every repo)

  • Format: 4-space, width 140, double quotes, semicolons, trailing commas, LF line endings (useEditorconfig: false, so this file is the sole authority — see above).
  • useExhaustiveDependencies: off — noise-by-nature on correct React effect/RHF code.
  • noArrayIndexKey: warn — kept on (catches real dynamic-list bugs); genuine static-list exceptions get a documented per-line biome-ignore.
  • noConsole off for scripts/** + logger.js; CSS/SCSS not linted; the icon module's mixed export allowed.

Product-specific one-offs (a bespoke file that co-exports, etc.) still use a local overrides entry or a documented inline biome-ignore in that product.

Versioning

Published from the webority-ui monorepo on each release, in lockstep with the other @webority/* packages. Pin a version; bump to adopt policy changes deliberately.