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

observed-properties

v3.0.1

Published

Observed properties for web components.

Downloads

9

Readme

Observed Properties

Observed properties for web components.

Build Status Coverage Status

Have you ever wondered why native web components have an API to handle attribute changes but not property changes?

This script implements both observedProperties and propertyChangedCallback that behave just like observedAttributes and attributeChangedCallback do.

In the background, it uses ES6 setters to cause a side-effect — run the callback method — everytime a property changes.

Install

npm install observed-properties --save

Import

Import withObservedProperties.

import withObservedProperties from 'observed-properties';

Use the whole path to the index.js file if you want the script to work on modern browsers natively, without having to depend on a build process.

import withObservedProperties from './node_modules/observed-properties/src/index.js';

Enhance HTMLElement

Enhance the HTMLElement by passing it to the withObservedProperties helper.

const EnhancedHTMLElement = withObservedProperties(HTMLElement);

Extend

Create a new web component class that extends EnhancedHTMLElement.

class TopTen extends EnhancedHTMLElement {}

Observe changes

Tell the component which properties to observe by setting observedProperties.

class TopTen extends EnhancedHTMLElement {
  static get observedProperties () {
    return ['songs'];
  }
}

React to changes

Set propertyChangedCallback, the method that will be run everytime a property changes.

class TopTen extends EnhancedHTMLElement {
  static get observedProperties () {
    return ['songs'];
  }

  propertyChangedCallback (propName, oldValue, value) {
    if (propName === 'songs' && oldValue !== value) {
      this.render(value);
    }
  }
}

Complete example

import withObservedProperties from 'observed-properties';

const EnhancedHTMLElement = withObservedProperties(HTMLElement);

class TopTen extends EnhancedHTMLElement {
  static get observedProperties () {
    return ['songs'];
  }

  constructor () {
    super();
    this.attachShadow({ mode: 'open' });
  }

  propertyChangedCallback (propName, oldValue, value) {
    if (propName === 'songs' && oldValue !== value) {
      this.render(value);
    }
  }

  render (value = []) {
    this.shadowRoot.innerHTML = `
      <dl>
        ${value.map(song => `
          <dt>${song.name}</dt>
          <dd>${song.artist} – ${song.year}</dd>
        `).join('')}
      </dl>
    `;
  }
}

window.customElements.define('top-ten', TopTen);

Known issues

This script does not play along with Polymer, SkateJS and possibly other web component libraries. The reason is that they use the same approach to detect property changes and it causes conflicts.

Another possible approach would be to use ES6 Proxies, but they are known to have performance issues and, if you are using a web component library, then you probably already have a way to detect property changes.