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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@runnerty/executor-js

v3.0.3

Published

Runnerty module: JS executor

Downloads

45

Readme

NPM version Downloads

JS executor for Runnerty:

Module for the execution of JS through a child process of nodejs (fork).

Installation:

npm i @runnerty/executor-js

You can also add modules to your project with runnerty-cli

npx runnerty-cli add @runnerty/executor-js

This command installs the module in your project, adds example configuration in your config.json and creates an example plan of use.

If you have installed runnerty-cli globally you can include the module with this command:

rty add @runnerty/executor-js

Configuration:

Add in config.json:

{
  "id": "js_default",
  "type": "@runnerty-executor-js"
}
{
  "id": "js_default",
  "type": "@runnerty-executor-js",
  "timeout": true,
  "debug": true
}

Plan:

Add in plan.json:

In case the script contains only one function, it is not necessary to specify it. Don't forget to include this in your script: module.exports = function_name.

{
  "id": "js_default",
  "script": "./js/sample.js"
}

If your script contains several exported functions you must indicate the function to execute. Don't forget to include this in your script for each of the functions you want to export: module.exports.functionSample = functionSample.

{
  "id": "js_default",
  "script": "./js/sample.js",
  "function": "functionSample"
}

In the parameters property you can indicate any type/value you expect in your function.

{
  "id": "js_default",
  "script": "./js/sample.js",
  "function": "functionSample",
  "parameters": 123
}
{
  "id": "js_default",
  "script": "./js/sample.js",
  "function": "functionSample",
  "parameters": {
    "id": "X123",
    "name": "Runnerty"
  }
}

Output (Process values):

Standard

  • PROCESS_EXEC_DATA_OUTPUT: Output data (JSON or String)
  • PROCESS_EXEC_ERR_OUTPUT: Error output message.

Extra

In case your function returns an object or an array of objects, you can also access each of the values individually.

For example, if your function returns this object:

{ "id": 1, "name": "mokka" }

You can access the values with the GETVALUE function indicating the key: @GV(PROCESS_EXEC_ID), @GV(PROCESS_EXEC_NAME)

Si su función devuelve este array de objeto:

[
  { "id": 1, "name": "mokka" },
  { "id": 2, "name": "cleo" },
  { "id": 3, "name": "nela" }
]

You can access the values with the GETVALUE function indicating the position and the key: @GV(PROCESS_EXEC_0_ID), @GV(PROCESS_EXEC_0_NAME)