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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@lightcode/node-red-utils

v0.2.0

Published

Utils for node-red @npm-lightcode packages

Downloads

5

Readme

Decription

Utils for node-red @npm-lightcode packages

Usage

To use this utils package in editor, you must :

  1. setup the editor javascript for your plugin as a module
  2. copy the src/editor.js file into your plugin ressource folder

Example

Your plugin file structure should look like this :

├── package.json
├── README.md
├── resources
│   ├── mynode-editor.js
└── src
    ├── mynode.html
    └── mynode.js

Write your Node-Red editor plugin mynode.html as you would normally, but move the editor javascript from your html file mynode.html to a dedicated file mynode-editor.js (the name don't have to end in -editor, it's just here for a clear example) and import it like this :

<script type="text/x-red" data-template-name="github-octokit">
[Your editor template]
</script>

<script type="text/x-red" data-help-name="github-octokit">
[Your editor help template]
</script>

<script type="module" src="resources/@yourscope/node-red-contrib-my-node/mynode-editor.js"/>

{% note %}

Note: You can omit the @yourscope part if your npm package don't have a scope. Keep in mind that Node-Red recommends to have one

{% endnote %}

This is needed because you must import your editor javascript as a module to be able to use import

Finally you need to copy the editor utils file into your ressource directory when you package it, via a package.json script :

{
  ...
  "scripts": {
    ...
    "prepack": "cp node_modules/@lightcode/node-red-utils/src/editor.js resources/editor-utils.js"
    ...
  }
  ...
}

The editor utils classes are now importable from the file mynode-editor.js :

import { MultiTypeField } from "./editor-utils.js"

Documentation

See the doc folder