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

be-vigilant

v0.0.27

Published

Add mutation observer to element, and broadcast mutations.

Downloads

37

Readme

be-vigilant

Add mutation observer to element.

Playwright Tests NPM version

Size, including be-decorated framework:

How big is this package in your project?

Size of new code:

Use case I: Many UI libraries are built around communicating between elements via events. be-vigilant translates mutation changes into events.

<div be-vigilant=my-event-name>
...
</div>

Event my-event-name is fired from the div element when the direct children of the div element change.

If the value of the attribute isn't specified, the default event name is be-vigilant-changed:

<div be-vigilant>
...
</div>

Use case II: be-vigilant also provides a brute-force way of sniffing out be-decorated adorned elements, even behind nooks and crannies of the DOM. be-decorated behaviors search for elements based on css observing, but sometimes those aren't always picked up.

For example:

<select>
    <template be-repeated></template>
</select>

Using the standard ways be-decorated elements are registered via css animation queries, this template simply won't be registered.

be-vigilant will cause it to register, if instructed to do so:

<select be-vigilant='{
    "forBs": true
}'>
    <template be-repeated></template>
</select>

To fine tune how the mutation observer is configured:

<div be-vigilant='{
    "subtree": true,
    "dispatchInfo": "my-event-name"
}'>
...
</div>

Another option, matchActions, provides the ability to specify different event names, based on css match tests on the mutated elements.

CDN

To use from a CDN:

<script type='module' crossorigin='anonymous'>
    import 'https://esm.run/be-vigilant';
</script>