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-icons-lwc

v1.1.0

Published

Webpipeline Icons — Lightning Web Components

Readme

@mmg-dev/webpipeline-icons-lwc

Lightning Web Components aus der webpipeline-icons-Monorepo — für Salesforce-Projekte und Standalone-Nutzung. Jede Komponente besteht aus einem HTML-Template und einem JavaScript-Controller.

Installation

pnpm i -D @mmg-dev/webpipeline-icons-lwc

LWC-Runtime-Dependencies (@lwc/engine-dom, @lwc/synthetic-shadow, @lwc/wire-service) werden automatisch mitinstalliert.

Hinweis: Die Beispiele verwenden pnpm. Alternativ funktionieren npm oder yarn analog (npm i -D, yarn add -D).

Standalone (außerhalb von Salesforce)

Das Bundle registriert automatisch alle Custom Elements beim Import:

import '@mmg-dev/webpipeline-icons-lwc';

Danach sind alle Icons als Custom Elements verfügbar:

<!-- Standard (24×24) -->
<icon-navigation-arrow-down></icon-navigation-arrow-down>

<!-- Benutzerdefinierte Größe -->
<icon-navigation-arrow-down width="32" height="32"></icon-navigation-arrow-down>

Salesforce DX (SFDX-Projekt)

Für Salesforce-Projekte die Source-Komponenten aus src/ in das eigene LWC-Verzeichnis kopieren:

cp -r node_modules/@mmg-dev/webpipeline-icons-lwc/src/components/* force-app/main/default/lwc/

Dann in einer LWC-Komponente importieren:

// myComponent.js
import { LightningElement } from 'lwc';

export default class MyComponent extends LightningElement {}
<!-- myComponent.html -->
<template>
  <c-icon-navigation-arrow-down></c-icon-navigation-arrow-down>
  <c-icon-navigation-arrow-down width="32" height="32"></c-icon-navigation-arrow-down>
</template>

In SFDX wird der Namespace-Prefix c- automatisch vorangestellt.

Farbe über CSS

icon-navigation-arrow-down {
  color: var(--color-primary-500);
}

Vollständiges Standalone-Beispiel

<!DOCTYPE html>
<html lang="de">
<head>
  <meta charset="UTF-8" />
  <title>LWC Icons Demo</title>
  <script type="module">
    import '@mmg-dev/webpipeline-icons-lwc';
  </script>
</head>
<body>
  <icon-navigation-arrow-down></icon-navigation-arrow-down>
  <icon-alert-cancel-circle-filled
    width="32"
    height="32"
    aria-label="Fehler"
  ></icon-alert-cancel-circle-filled>
</body>
</html>

Accessibility

<!-- Dekorativ (Default): aria-hidden="true" -->
<icon-navigation-arrow-down></icon-navigation-arrow-down>

<!-- Semantisch: mit sichtbarem Titel -->
<icon-navigation-arrow-down icon-title="Nach unten"></icon-navigation-arrow-down>

<!-- Semantisch: mit Screen-Reader-Label -->
<icon-navigation-arrow-down aria-label="Nach unten scrollen"></icon-navigation-arrow-down>
  • Dekorativ (Default): aria-hidden="true" — Icon wird von Screen Readern ignoriert
  • Semantisch: Wenn icon-title oder aria-label gesetzt ist → aria-hidden wird entfernt, role="img" gesetzt

Empfehlung: Icons neben Text sind in der Regel dekorativ. Alleinstehende Icons (z.B. Icon-Buttons) brauchen ein aria-label.

Props

| Prop | Typ | Default | Beschreibung | | ------------ | -------- | ------- | -------------------------------------------- | | width | number | 24 | Breite in Pixel | | height | number | 24 | Höhe in Pixel | | icon-title | string | — | Rendert <title> im SVG, setzt role="img" | | aria-label | string | — | Screen-Reader-Label, setzt role="img" |

Naming

| Kontext | Format | Beispiel | | ------- | --------------- | ------------------------------ | | LWC Tag | <icon-{name}> | <icon-navigation-arrow-down> |