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

node-red-contrib-jktesting

v0.4.0

Published

An experimental node for Node-RED for learning and testing node creation ideas. Can also be used as a template for your own nodes.

Readme

node-red-contrib-jktesting

An EXPERIMENTAL Node-RED testing/learning set of nodes.

Designed as an experimental learning and testing tool for trying out different things when designing Node-RED nodes.

You can also use it as a template for writing your own nodes.

This node has several purposes:

  1. Learn the order of execution and events for learning how to program you own nodes.
  2. Show some best practices and standards for code when developing your own nodes.
  3. Act as a template I or you can use for your own nodes.

Node Creation Workflow

The workflow I use to create new nodes is:

  1. Create a new repo on GitHub - don't yet tag it with node-red until you are ready to go public
  2. Clone the repo to my source files folder on the dev machine
  3. Manually create a soft-link from the new folder into ~/.node-red/node_modules (I don't use npm link as that does strange things like creating a global link)
  4. Create the package.json, README.md, LICENCE, CHANGELOG.md, .gitignore files in my source folder. Create a sub-folder called "nodes" and create the html and js files in there.
  5. In the source folder, do npm install if you need to install any dependencies
  6. Restart Node-RED.

Design

Physical file/folder location summary

Folders and files for resources on the device running Node-RED are:

Known Issues

To Do

Changes

See the Change Log for details.

Pre-requisites

See the package.json file for details.

Requires at least Node.JS v6 and Node-RED v0.16

Install

Run the following command in your Node-RED user directory (typically ~/.node-red):

npm install node-red-contrib-jktesting

Run Node-RED and add an instance of the test node.

There is also a simple example in the library.

Nodes

JK Simple Test (jktest)

Node Instance Settings

Each instance of the test node has the following settings available.

Inputs

Outputs

  • Standard output

Discussions and suggestions

Use the Node-RED google group for general discussion about this node. Or use the GitHub issues log for raising issues or contributing suggestions and enhancements.

Contributing

If you would like to contribute to this node, you can contact Totally Information via GitHub or raise a request in the GitHub issues log.

Developers/Contributors