node-red-contrib-unsafe-function v0.8.0
node-red-contrib-unsafe-function
The fast and furious version of function nodes.
Uses require-from-string instead of executing the function inside a vm.
The implementation sticks to the api of the standard function nodes,
so if your code worked on a standard function node it should also work on unsafe-function (only faster!).
unsafe-function does not run inside a vm and therefore may do unsafe operations
(like calling require('fs') and its operations).
Additional Features
nodeRedContribUnsafeFunctionAsyncSend, nodeRedContribUnsafeFunctionAsyncReceive -
Set these RED settings variables in order to make the sending\receiving of messages asynchronous.
The current behavior of node-red is that sending a message pauses until all the following nodes
in the flow finish handling the sent message (unless they specifically do it asynchronously).
For more information, see issue 833.
nodeRedContribUnsafeFunctionProfiling: Set this RED settings variable to show
for each node a status message with basic profiling information: how many messages
were handled and what's the total\max execution time.
Change Log
From 0.3.0 to 0.4.0
- Using global RED settings
nodeRedContribUnsafeFunctionAsyncSend,nodeRedContribUnsafeFunctionAsyncReceiveandnodeRedContribUnsafeFunctionProfiling, instead of checkingNODE_RED_CONTRIB_UNSAFE_FUNCTION_ASYNC_SEND,NODE_RED_CONTRIB_UNSAFE_FUNCTION_ASYNC_RECEIVEandNODE_RED_CONTRIB_UNSAFE_FUNCTION_PROFILINGenvironment variables. - Updating package dependency
require-from-stringto version 1.2.1.