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-mp-function

v1.1.1

Published

Multi-threaded function node for NODE-RED

Readme

node-red-contrib-mp-function

Install


$ npm i node-red-contrib-mp-function

Or globally alongside Node-RED:


sudo npm i -g node-red-contrib-mp-function

You will need to restart Node-RED for it to pick-up the new nodes.

Changes in 1.1.1

fix Sometimes script is not catching configuration in non-persistent mode.

Changes in 1.1.0

new Added persistent option. When OFF new threads are created when new message arrives and are terminated when work is complete (thread limit and message caching also works). When ON, threads are waiting for messages as usual. new Command line for worker thread now contains name of the node. So you can kill it with fire, if anything happens.

Changes in 1.0.5

new Change from round-robin message distribution to load-balanced. When all threads are loaded incoming messages are queued. When thread calculation is finished, node will check inner message queue for new tasks. fix Fix vm context failure on creation of new script setup.

Usage

node-red-contrib-mp-function is based on original IBM function node. You need to see it basic usage at first. This node allows you to run your hardcore calculation code in separate process (or some of them) without freezing of node-red process and your other precious flows.

Customization

As you can import some external npm modules from node-red configuration? you can provide them into this node in 'Requires' field. The string must contain a name prefered for usage in your code and module name (or path to it) connected by an '<-' and joined by colon. For example:

canvas<-canvas,mylovelymodule<-/path/to/mylovelymodule.js,gzip<-zlib

The imported modules are accessible via context.global.yourmodulename for compatibility with original module

Limitations

You can not use context, flow or global variables... yet. Write necessary info to the msg var before passing it into node. Event handlers on node variable also do not work. And probably wont.

But you can print messages with node.log, node.warn and node.error. And you can use statuses as well.

License

MIT License