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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@browser-modules/buttons

v1.0.8

Published

Button Web Component using ES6 modules

Downloads

4

Readme

Button

API Documentation

Over engineered web component button with:

  1. Declarative Interface
  2. Imperative Interface
  3. Finite State Machine
  4. Custom Styling and HTML Template

Dependencies

    graph TD;
    A[Buttons]
    A --> B[Utility Service]
    B --> C[Template loader]
    A --> D[Component]
    D --> E[Declaration]
    D --> F[Configuration]
    D --> G[Metadata]
    D --> H[Styling]
    A --> I[Modules]
    I --> L[Machine]
    I --> K[Events]
    I --> J[Dictionary]
    L --> K
    K --> J

module dependencies are managed using NPM Packages.

{  "dependencies": {
    "@browser-modules/dictionary": "^1.0.8",
    "@browser-modules/events": "^1.1.1",
    "@browser-modules/machine": "^1.0.2",
    "@browser-modules/web.component": "^1.0.9"
  }
}

To enable the browser to find the modules, HTML Importmaps is used:

<script type="importmap">
  {
    "imports": {
      "@browser-modules/dictionary": "../node_modules/@browser-modules/dictionary/lib/dictionary.js",
      "@browser-modules/events": "../node_modules/@browser-modules/events/lib/events.js",
      "@browser-modules/machine": "../node_modules/@browser-modules/machine/lib/machine.js",
      "@browser-modules/web.component": "../node_modules/@browser-modules/web.component/lib/component.js"
    }
  }
</script>

The finite state machine is an optional module which enable the support of complex workflows. This is a good example of how the dependency tree works.

External dependencies is simply loaded using the import keyword, as declared in the different modules:

// Inside Machine
import { Event as Emitter } from "@browser-modules/events";

// Inside Events
import { Dictionary } from "@browser-modules/dictionary";

Running Demo

To explore and manually interact with the the components imperative interface follow these steps:

  1. Get Started:

    1. Start Live Server and verify the component is visible in Chrome Browser
    2. Open Developer Tools in Chrome Browser
    3. Select the Console in the Developer Tools
    4. Verify the component loaded successfully
  2. Load the component into the Console:

var button = document.querySelector("button-pin");