From bbff7403fbf46f9ad92240ac213df8d30ef31b64 Mon Sep 17 00:00:00 2001 From: Florian Dold Date: Thu, 20 Sep 2018 02:56:13 +0200 Subject: update packages --- node_modules/spawn-wrap/README.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) (limited to 'node_modules/spawn-wrap/README.md') diff --git a/node_modules/spawn-wrap/README.md b/node_modules/spawn-wrap/README.md index 0cac17fa5..428df37e5 100644 --- a/node_modules/spawn-wrap/README.md +++ b/node_modules/spawn-wrap/README.md @@ -52,6 +52,20 @@ process.on('exit', function (code) { require('spawn-wrap').runMain() ``` +## ENVIRONMENT VARIABLES + +Spawn-wrap responds to two environment variables, both of which are +preserved through child processes. + +`SPAWN_WRAP_DEBUG=1` in the environment will make this module dump a +lot of information to stderr. + +`SPAWN_WRAP_SHIM_ROOT` can be set to a path on the filesystem where +the shim files are written in a `.node-spawn-wrap-` folder. By +default this is done in `$HOME`, but in some environments you may wish +to point it at some other root. (For example, if `$HOME` is mounted +as read-only in a virtual machine or container.) + ## CONTRACTS and CAVEATS The initial wrap call uses synchronous I/O. Probably you should not -- cgit v1.2.3