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

element-notifier

v1.1.2

Published

A MutationObserver dis/connected helper

Readme

element-notifier

A MutationObserver dis/connected helper.

import {notify} from 'element-notifier';

const observer = notify(
  // callback that receives any connected/disconnected element
  (element, connected) => {
    if (connected)
      console.log(element, 'has been connected');
    else
      console.log(element, 'has been disconnected');
  },

  // optional arguments
  document,         // the root element to observe
  MutationObserver  // a MutationObserver (non DOM envs)
);

The observer is a regular MutationObserver instance with a self bound, and instrumented, .observe(node) method to observe mutations within fragments too (example: shadowRoot nodes).

Why?

The MutationObserver dance with records is easily error prone:

  • records are triggered lazily in a bizarre order
  • records are related to single containers, but inner elements are not notified
  • it's difficult to ensure that within a MutationObserver callback, all elements, in the right order of events, get passed along uniquely per event

This helper does just this: it passes to the callback every element that has been added, or removed, from the document.

About ShadowDOM

While the observer could crawl nodes within a shadowRoot, in case it's opened, if nodes are removed from it nothing is notified due MutationObserver limitations.

If observing nodes appended or removed from any shadowRoot is desired, or at least any open one, it is necessary to somehow pollute the Element.prototype in a similar way:

import {notify} from 'element-notifier';

// augmented method with right options included
const {observe} = notify(/* ... */);

const {attachShadow} = Element.prototype;
Element.prototype.attachShadow = function (init) {
  const shadowRoot = attachShadow.call(this, init);
  if (init.mode === 'open')
    observe(shadowRoot);
  return shadowRoot;
};

It is not responsibility of this module to augment the environment so it's up to this module consumers decide if doing so is needed or desired.

Please note that connected might mislead in case the shadowRoot is not live yet, as the MutationObserver in fragments doesn't care about their owner state.