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

@mfp-design-system/stepper

v5.0.0

Published

Stepper (mfp-stepper / mfp-step) for multi-step flows: onboarding, checkout, forms.

Downloads

1,276

Readme

@mfp-design-system/stepper

A stepper for multi-step flows — onboarding, checkout, multi-page forms, lesson progress. Two custom elements: <mfp-stepper> (orchestrator) and <mfp-step> (each step).

Install

npm install @mfp-design-system/stepper @mfp-design-system/tokens

Usage

import '@mfp-design-system/stepper';
import '@mfp-design-system/tokens/css';
<mfp-stepper current="1">
    <mfp-step label="Account"></mfp-step>
    <mfp-step label="Profile"></mfp-step>
    <mfp-step label="Preferences"></mfp-step>
    <mfp-step label="Done"></mfp-step>
</mfp-stepper>

Each step's status is derived automatically. Status colors map to meaning, not brand — green for success, yellow for in-progress, red for error:

  • index < currentcompleted (checkmark, green)
  • index === currentcurrent (yellow outline, pulsing yellow dot)
  • index > currentpending (step number, muted)
  • any step with [error]error (X mark, red) — overrides the derived status

API

<mfp-stepper>

| Attribute | Type | Default | | ------------- | ---------------------------- | -------------- | | current | number | 0 | | orientation | 'horizontal' \| 'vertical' | 'horizontal' | | clickable | boolean | false |

Events:

  • step-click (only when clickable) — event.detail.index is the clicked step's index.

<mfp-step>

| Attribute | Type | Default | Description | | ------------- | ------- | ------- | -------------------------------------------- | | label | string | '' | Visible label | | description | string | '' | Optional sub-label (shown beneath the label) | | error | boolean | false | Overrides status to error |

Most state is set by the parent stepper during its sync pass. You don't typically read or write index, status, orientation, clickable, or total directly — though they're available as attributes if you want to style around them with ::part(...) or your own CSS.

Variants

Vertical

<mfp-stepper orientation="vertical" current="2">
    <mfp-step label="Account" description="Pick a username and password"></mfp-step>
    <mfp-step label="Profile" description="A photo and short bio"></mfp-step>
    <mfp-step label="Preferences" description="What updates do you want?"></mfp-step>
    <mfp-step label="Done" description="You're ready to go"></mfp-step>
</mfp-stepper>

With an error step

<mfp-stepper current="2">
    <mfp-step label="Choose plan"></mfp-step>
    <mfp-step label="Payment" error description="Card was declined"></mfp-step>
    <mfp-step label="Confirm"></mfp-step>
</mfp-stepper>

Clickable (for "free navigation" flows like settings wizards)

<mfp-stepper current="1" clickable @step-click="onJump">
    <mfp-step label="Profile"></mfp-step>
    <mfp-step label="Security"></mfp-step>
    <mfp-step label="Notifications"></mfp-step>
</mfp-stepper>
function onJump(e) {
    console.log('Jumped to step', e.detail.index);
}

Shadow parts

For custom styling: ::part(circle), ::part(label), ::part(description), ::part(connector).

A11y

  • The current step has aria-current="step"
  • Each step has an aria-label that includes its status (e.g., "Profile — in progress", "Payment — error")
  • Clickable steps are exposed as role="button" and accept Enter / Space
  • Pulse animation honors prefers-reduced-motion

Framework notes

Same as the rest of the suite — Vue/Nuxt need isCustomElement, Angular needs CUSTOM_ELEMENTS_SCHEMA, React 19+ works natively.