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

@tonymacdonald/node-red-msg-encapsulation

v0.0.4

Published

Wrap existing message as a property in a new message or extract a previously wrapped message

Downloads

4

Readme

node-red-msg-encapsulation

A pair of simple nodes to wrap an incoming node red message into a property of a new, otherwise empty, message and to, later, unwrap the previously wrapped message. This allows the state carried in the original message to be preserved for later use while still being carried along with the message.

Example

example

Nodes

nodes

wrap-msg

Outputs

| output | description | | --- | --- | | wrapped_msg (object) | the entire incoming message. |

Details

The entire incoming message is wrapped into a property msg.wrapped_msg on a new otherwise empty message which is sent on the output.

unwrap-msg

Inputs

| input | description | | --- | --- | | wrapped_msg (object) | the original wrapped message object to be unwrapped. | payload | the payload to be added to the unwrapped message as msg.outer_payload

Output

| output | description | | --- | --- | | outer_payload | The payload of the incoming message | all other properties | The properties of the original wrapped message from msg.wrapped_msg on the incoming message.

Details

The previously wrapped message is extracted from the wrapped_msg property of the incoming message, The payload of the incoming message is preserved as a new property outer_payload added to the unwrapped message which is sent to the output.

The outer_payload propterty on the unwrapped message allows the result of the intervening flow to be integrated with the newly unwrapped message.

If there is no wrapped_msg property on the incoming message, a catchable error is raised.

Using the wrap-msg and unwrap-msg nodes around a destructive section of the flow allows for processing on the intervening flow without owerwriting properties of the wrapped message.