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

@kumologica/devkit

v4.0.1

Published

Module used to develop contrib nodes for Kumologica runtime

Readme

README

For impatients, you can jump to the test folder to see a simple node. However, we will recommend to read this guide as there are naming conventions that every single kumologica developer will have to follow to develop contrib nodes.

Project structure

Contrib nodes will be made of two files:

  • a js file that defines the behaviour at runtime of the node
  • an html file that defines and captures the properties of the node from the designer

The whole project will be bundled together with a package.json

package.json

kumologica imposes the following convention into this file:

  • name: it will follow the convention /kumologica-contrib-
  • kumologica: This property will be responsible to register all the nodes that your contrib module is exporting

Example:

{
  "name": "@acme/kumologica-contrib-echo",
  "kumologica": {
    "nodes": {
      "echo": "echo.js"
    }
  }
}

The JS file

module.exports = function(App) {
  const { KLNode } = require('@kumologica/devkit');

  class Echo extends KLNode {
    constructor(props) {
      // Do not forget to call the constructor!!
      super(App, props);
      this.message = props.message;
    }

    handle(msg) {
      App.log.info(`Echo node says: ${this.message}`);
      this.send(msg);
    }
  }
  //  Do not forget to register the node
  App.nodes.registerType('echo', Echo);
};

This node is named Echo, and the runtime will ensure to invoke the handle method when a message is received by the node.

A few points to remember here:

  • Do not forget to extend from KLNode, otherwise your node will not receive any message.
  • Do not forget to override the method handle.
  • send method can be invoked to send the message linked as an output in the designer.

The HTML file

This file provides the following:

  • Registration with the designer
  • A window to capture the properties to the node
<script type="text/x-kumologica" data-template-name="echo">
  <!-- name field -->
  <div class="form-row">
      <label for="node-input-name">
        <span>Name</span>
      </label>
      <input type="text" id="node-input-name" placeholder="Display name">
  </div>

  <!-- message field -->
  <div class="form-row" style="margin-bottom:0px">
    <label for="node-input-message">
        <span>Message</span>
    </label>
    <input type="text" id="node-input-message">
  </div>
</script>

<script type="text/javascript">
  App.nodes.registerType('echo', {
    category: 'echo_contrib',
    icon: 'browser.png',
    color: '#FFF59D',
    defaults: {
      name: { value: '' },
      message: { value: '' }
    },
    inputs: 1,
    outputs: 1,
    label: function() {
      return this.name || 'echo';
    }
  });
</script>

| WARNING: the category property only takes alphanumerical and _ which will be replaced by a whitespace in the designer | | ------------------------------------------------------------------------------------------------------------------------- |

All the icons will need to placed in the directory called icons in the same directory that the html and js files are.