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

@karesztrk/baseline-status

v1.1.0

Published

A widget displaying Baseline status of a web feature

Readme

<baseline-status> web component

A widget displaying Baseline status of a web feature based on https://github.com/web-platform-dx/web-features data.

This is a thin fork of the original repo.

Advantages

  • It's not built on a larger web component library
  • It's using a tiny and simple base class
  • Compressed icons
  • Web component name is customizable
  • You can bring your own icons (eg. boneless)

Example

Show Baseline status widget for anchor-positioning:

<baseline-status featureId="anchor-positioning"></baseline-status>
<!-- <baseline-icon support="limited"></baseline-icon> -->

Register the BaselineStatus and optionally BaselineIcon web components.

import { BaselineStatus, BaselineIcon } from "@karesztrk/baseline-status";

customElements.define("baseline-icon", BaselineIcon);
customElements.define("baseline-status", BaselineStatus);

Or you can use the static helper

import { BaselineStatus } from "@karesztrk/baseline-status";

class YourComponent extends BaselineStatus {
  static {
    this.register("baseline-status", YourComponent);
  }
}

export default YourComponent;

Custom icons

You can register your own icons with the BonelessStatus web component. Where does this name is coming from? Check this blog post from Adam. Why? Wrapping SVG images inside JS files increases the bundle size and blocks the caching capability of modern browsers.

import { BonelessStatus, BaselineIcon } from "@karesztrk/baseline-status";

customElements.define("baseline-icon", BaselineIcon);
customElements.define("baseline-status", BonelessStatus);
<boneless-status featureId="array">
  <template id="icons">
    <svg slot="chrome"></svg>
    <svg slot="edge"></svg>
    <svg slot="firefox"></svg>
    <svg slot="safari"></svg>
    <svg slot="available"></svg>
    <svg slot="unavailable"></svg>
    <svg slot="no_data"></svg>
  </template>
</boneless-status>

Usage

Install and bundle with your application.

Install

pnpm install @karesztrk/baseline-status
# or npm install @karesztrk/baseline-status

See docs for example usage in HTML.

See rollup.config.js for an example of a bundler configuration.

Development

Run locally:

pnpm run serve

The local server uses wds @web/dev-server package. To enable web component related polyfills for legacy browsers, it uses @web/dev-server-legacy package. See web-dev-server.config file for the exact configuration.