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

compop

v0.1.5

Published

JavaScript function to pop component configuration off a global stack and construct corresponding class instances

Downloads

3

Readme

ComPop

A JavaScript framework for server side markup.

This framework exposes a function to pop component configuration off a global storage array (stack || queue*) and construct a corresponding class instance for each configuration in the array. It also aims to promote encapsulation for components and utilizes a thin wrapper around CustomEvent to provide a mechanism for communication between isolated components.

Installation

npm install --save compop

Usage

  1. Scaffold out the global components array and optional state object and storage mechanism in your HTML layout file. Note: the "YOUR_SITE_GLOBAL" key is a convention to encapsulate your components from other scripts in the window
<!-- templates/layout.html -->

<html>
    <head>
        <title>Your Site</title>
    </head>
    <body>
        <script>
            window['YOUR_SITE_GLOBAL'] = { components: [], state: {} , storage: 'queue' };
        </script>

        ...Your HTML components...

        <script src="/scripts/main.js"></script>
    </body>
</html>
  1. Add HTML components to your site - in any templating language - and push a component config onto the glbal array.
<!-- templates/components/component-handle.html -->

<div id="unique-identifier" class="component-handle">

    ...Your component markup...

    <script>
        window['YOUR_SITE_GLOBAL'].components.push({
            handle: 'component-handle', // Required to match your component class in the classMap
            id: 'unique-identifier', // Recommended to encapsulate scope for your component class
            // ...any other variables for your component class
        });
    </script>
</div>
  1. Construct all instances of your components from the corresponding configuration objects specified in the markup.
// src/scripts/components/component-handle.js

export default class {
    constructor({
        id,
        // ...any other variables for your component class
        state,
        actions,
        events,
        refresh,
    }) {
        // Define elements and variables needed by the component
        const el = document.getElementById(id);

        // Define component functionality
        function handleCustomAction(e) {
            // Get any information from the event
            const { customData } = e.detail;

            // Do something with custom data in response to the event
            ...

            // Communicate that something has happened
            events.emit(actions.someThing, { time: + new Date() });
        }

        // Attach any event listeners
        window.addEventListener(actions.myComponentCustomAction, handleCustomAction);
    }
}
// src/scripts/main.js

import pop from 'compop'

import ComponentClass from './components/component-handle.js';

const classMap = {
    'component-handle': ComponentClass
};

const actions = {
    myComponentCustomAction: 'my-component-custom-action',
    someThing: 'SOME_THING'
}

// Construct components on DOM content loaded
function handleDOMConentLoaded() {
    const scaffold = window[SITE_HANDLE];

    function cb({ events, refresh }) {
        // Do something after components initialize
    }

    // Call component constructors
    pop({ scaffold, classMap, actions, cb });
}

// Attach event listener
document.addEventListener('DOMContentLoaded', handleDOMConentLoaded);