What you want here is options.detached of spawn. Setting this option will allow the sub-process to continue even after the main process calling spawn has terminated.

Quoting the documentation:

On Windows, setting options.detached to true makes it possible for the child process to continue running after the parent exits. The child will have its own console window. Once enabled for a child process, it cannot be disabled.

On non-Windows platforms, if options.detached is set to true, the child process will be made the leader of a new process group and session. Note that child processes may continue running after the parent exits regardless of whether they are detached or not. See setsid(2) for more information.

Basically this means what you "launch" keeps running until it actually terminates itself. As 'detached', there is nothing that "ties" the sub-process to the execution of the parent from which it was spawned.

Example:

listing of sub.js:

(async function() {

  try {

    await new Promise((resolve,reject) => {
      let i = 0;
      let ival = setInterval(() => {
        i++;
        console.log('Run ',i);
        if (i === 5) {
          clearInterval(ival);
          resolve();
        }
      }, 2000);
    });

  } catch(e) {
    console.error(e);
  } finally {
    process.exit();
  }

})();

listing of main.js

const fs = require('fs');
const { spawn } = require('child_process');

(async function() {

  try {

    const out = fs.openSync('./out.log', 'a');
    const err = fs.openSync('./out.log', 'a');

    console.log('spawn sub');

    const sub = spawn(process.argv[0], ['sub.js'], {
      detached: true,               // this removes ties to the parent
      stdio: [ 'ignore', out, err ]
    });

    sub.unref();
    console.log('waiting..');

    await new Promise((resolve,reject) =>
      setTimeout(() => resolve(), 3000)
    );
    console.log('exiting main..');

  } catch(e) {
    console.error();
  } finally {
    process.exit();
  }

})();

The basics there are that the sub.js listing is going to output every 2 seconds for 5 iterations. The main.js is going to "spawn" this process as detached, then wait for 3 seconds and terminate itself.

Though it's not really needed, for demonstration purposes we are setting up the spawned sub-process to redirect its output ( both stdout and stderr ) to a file named out.log in the same directory.

What you see here is that the main listing does it's job and spawns the new process then terminates after 3 seconds. At this time the sub-process will only have output 1 line, but it will continue to run and produce output to the redirected file for another 7 seconds, despite the main process being terminated.