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

@pmdartus/event-visualizer

v3.0.0

Published

A visualization tool to better understand how events propagate in the shadow DOM

Downloads

9

Readme

Event visualizer

A visualization tool to better understand how events propagate in the shadow DOM.

Build status NPM

Overview

The way DOM events propagate in the shadow DOM is not intuitive for developers onboarding with web components. Event configuration, DOM structure and closed vs. opened shadow trees are many factors influencing event propagation.

This project is an attempt to bring clarity to this subject by offering a visual playground explaining how events propagates step-by-step in the shadow DOM.

Event visualizer screenshot

Try it out: Demo / Playground

Installation

This package can be consumed as an NPM package.

$ npm install --save @pmdartus/event-visualizer

Alternatively for drop-in consumption this package can directly be loaded from Skypack CDN.

<script type="module" src="https://cdn.skypack.dev/@pmdartus/event-visualizer"></script>

<event-visualizer>

Properties / Attributes

| Property | Attribute | Type | Default | Description | | --------------- | ---------------- | --------- | --------------------- | ----------------------------------------------------------------------------------------------------------------------------------- | | label | label | string | "Event propagation" | The label name. | | eventBubbles | event-bubbles | boolean | false | Indicates wether the dispatched event should bubbles or not. | | eventComposed | event-composed | boolean | false | Indicates wether the dispatched event should be composed or not. |

Slots

| Name | Description | | ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | | default | Accepts a single <template> element representing the DOM tree to visualize. Refer to the DOM tree definition section for more details. |

DOM tree definition

The visualized DOM tree is configured by passing a <template> element in the default slot. The content of the template tag is interpreted by the <event-visualizer> custom element to render the visual previous of the DOM tree and emulate event dispatching:

  • Shadow trees can be defined directly in HTML via the declarative shadow DOM syntax with the difference difference that the shadow-root attribute is renamed to data-shadow-root.
  • The original event target is defined by adding a target attribute.
  • A label can be added to any element using the id attribute.
  • Restrictions:
    • The template content should have root element.
    • The DOM should have a one element with the target attribute.
<event-visualizer label="Simple tree">
  <template>
    <div id="a">
      <div id="b" target></div>
    </div>
  </template>
</event-visualizer>

<event-visualizer label="Simple shadow tree">
  <template>
    <div id="a">
      <template data-shadowroot="open">
        <div id="b" target></div>
      </template>
      <div id="c">
    </div>
  </template>
</event-visualizer>