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

@mmg-dev/webpipeline-biome-stencil

v1.2.0

Published

Shared Biome configuration for Webpipeline Stencil projects

Readme

@mmg-dev/webpipeline-biome-stencil

Shared Biome configuration for MMG Stencil/Web Component projects.

Replaces ESLint + Prettier with a single, faster tool.

Installation

When migrating from ESLint/Prettier, remove old dependencies and do a clean install to avoid stale packages:

pnpm remove eslint @mmg-dev/webpipeline-stencil-eslint-prettier-config
rm -rf node_modules pnpm-lock.yaml
pnpm i --save-dev @biomejs/biome @mmg-dev/webpipeline-biome-stencil

Also remove the "prettier" field from package.json and delete eslint.config.mjs if present.

Usage

Create a biome.json in your project:

{
  "$schema": "https://biomejs.dev/schemas/2.4.6/schema.json",
  "extends": ["@mmg-dev/webpipeline-biome-stencil"]
}

Scripts

Add these scripts to your package.json:

{
  "scripts": {
    "lint": "biome check src/",
    "lint:fix": "biome check --write src/",
    "format": "biome format --write src/"
  }
}

VS Code Integration

Install the Biome extension (Cmd+Shift+X → "biome").

Copy .vscode/settings.json from this package to your project, or add manually:

{
  "typescript.preferences.includePackageJsonAutoImports": "off",
  "editor.defaultFormatter": "biomejs.biome",
  "editor.formatOnSave": true,
  "editor.codeActionsOnSave": {
    "source.fixAll.biome": "explicit",
    "source.organizeImports.biome": "explicit"
  },
  "[typescript]": {
    "editor.defaultFormatter": "biomejs.biome"
  },
  "[javascript]": {
    "editor.defaultFormatter": "biomejs.biome"
  },
  "[typescriptreact]": {
    "editor.defaultFormatter": "biomejs.biome"
  },
  "[javascriptreact]": {
    "editor.defaultFormatter": "biomejs.biome"
  }
}

What's included

Formatter (replaces Prettier)

  • Single quotes, semicolons, trailing commas
  • Line width: 180 (matching previous Prettier config)
  • 2 spaces indent, LF line endings

Linter (replaces ESLint)

| ESLint Rule | Biome Equivalent | | ------------------------------------ | ------------------------------- | | @typescript-eslint/no-unused-vars | correctness/noUnusedVariables | | @typescript-eslint/no-explicit-any | suspicious/noExplicitAny | | no-console | suspicious/noConsole | | no-debugger | suspicious/noDebugger | | prefer-const | style/useConst | | no-var | style/noVar | | unused imports | correctness/noUnusedImports |

Not covered by Biome

The @stencil-community/eslint-plugin rules have no Biome equivalent. These were enforced via ESLint:

  • element-type, required-jsdoc, render-returns-host
  • methods-must-be-public, own-methods-must-be-private
  • strict-mutable, decorators-style, decorators-context
  • ban-prefix, prefer-vdom-listener

These are Stencil-framework-specific and must be enforced via code review or a separate ESLint pass if needed.

Local Development

To work with a local version of this package (e.g. for testing changes before publishing), add the following to your project's package.json under devDependencies:

{
  "devDependencies": {
    "@mmg-dev/webpipeline-biome-stencil": "link:../_npm-packages/webpipeline-biome-stencil"
  }
}

Then clean install:

rm -rf node_modules pnpm-lock.yaml
pnpm install

If you already have a pnpm-lock.yaml, a fresh install ensures the local link is resolved correctly. The relative path must point to your local clone of this repo. Adjust ../_npm-packages/... accordingly.

Once you're done testing, switch back to the npm version:

pnpm i --save-dev @mmg-dev/webpipeline-biome-stencil

Release

Releases are managed via standard-version, which handles version bumping, CHANGELOG generation, and git tagging based on Conventional Commits.

Workflow

  1. Make your changes and commit using conventional commit messages:
git commit -m "fix: disable linting for components.d.ts"
git commit -m "feat: add noConsole rule"
  1. Run the release script:
# auto-detect version bump (patch/minor/major) from commits
pnpm release

# or force a specific bump
pnpm release:patch   # 1.1.1 -> 1.1.2
pnpm release:minor   # 1.1.1 -> 1.2.0
pnpm release:major   # 1.1.1 -> 2.0.0

This will: bump version in package.json, update CHANGELOG.md, create a git tag, and publish to npm.

  1. Push the tag to remote:
git push --follow-tags

License

MIT