PATH environment variable being removed during spawn

[stuffaboutpete]

Out of the box, I was getting the following error:

Current git branch is master
Retrieving template currently deployed on stack example
Packaging template template.yml
ERROR: Error with command: Error: spawn aws ENOENT
    at Process.ChildProcess._handle.onexit (internal/child_process.js:264:19)
    at onErrorNT (internal/child_process.js:456:16)
    at processTicksAndRejections (internal/process/task_queues.js:77:11)

This is because the call to spawn the aws process specifies an options argument - if this is provided, the default value which contains a PATH key is not used. The following is a brute force fix, but you may prefer to extend the existing environment on each individual call to run:

// core/utils.js

run: (cmd, args=[], opts={}, onData=null) => {

  return new Promise((resolve, reject) => {
    if (!opts.env) opts.env = {};                         // New
    if (!opts.env.PATH) opts.env.PATH = process.env.PATH; // New

    let proc = spawn(cmd, args, opts)

I'm using Ubuntu on WSL 2 (Windows) so my setup may have something to do with it but I get the impression this will show up on other systems too. A couple of links I found:

https://stackoverflow.com/questions/27688804/how-do-i-debug-error-spawn-enoent-on-node-js

nodejs/node#12986