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

componentmanager

v1.0.4

Published

Manage your enviroment nodes

Downloads

2

Readme

ComponentManager

Manage your dom nodes to initialize. ComponentManager is written in EcmaScript6, alternative your can use es5 version with bower.

minimum system enviroment

  • Promise API
  • document.querySelectorAll

Example Markup

<button class="simple-button" data-components="button">label</button>

<div data-components="button,mycomponent" data-settings='{"button": {}, "mycomponent": {}}'></div>

Run

var cm = new ComponentManager();

// setup properties before start detection
cm.setup({PROPERTY:VALUE});

cm
// require event, will triggerd after found components
      .on('AddComponent', function (event) {
// EXAMPLE with Systemjs loader and flightjs components
        return System
          .import(event.path)
          .then(function (pack) {
            return pack.default;
          })
          .then(function (component) => {
            var componentNode = component.attachTo(event.node, event.setting);
          });
      })
// detect start by document as root 
      .detect(document)
// promise interface after done make the next step
      .then(function (nodes) {
        // all component found and initialize
      });

documentation

All handling based on promises objects, after detection you can play with a ready system. Each function return a valid value it follow the fluid code conzept

properties (options)

path

(default 'components/') prefixed script paths could be empty script

detectAttr

(default 'data-components') detection attribute of nodes

settingAttr

(default 'data-settings') optional attribute for setting definition(JSON script)

splitSeperator

(default ',') used for multi definition if components Example: data-components="comp1,comp2"

Methode

on(eventName, callback)

listener registration @param eventName @param callback @returns {ComponentManager}

setup(setting)

setup manager by map @param setting @returns {ComponentManager}

getComponentNodes(root)

return all component nodes in root @param root @returns {NodeList}

getNodesOfComponent(componentName, root = document)

return all nodes that implement the component @param componentName @param root @returns {NodeList}

detect(root)

detect all components in root @param root @returns {Promise}

Events

AddComponent

Will trigger after detection and parsing all information for this component Event data has information about this component { node = DOM Node name = component name, path = path to component, setting = detected setting }