fix(v1): safer handling of child process exits

[ochicf]

This MR attempts to improve how child process exits are handled.

Problems I encountered and solved by this fix:

• infinite process indicator when child process exited due to unhandled errors. In my case it happened because of broken installation was thrown because of a missing package
• calling process.exit(0) caused that the caller process never receive the message sent with process!.send(...), even when sucessful (not sure why this happens). Just setting process.exitCode and letting the process to end normally worked well

Notes:

• I added a loadAndExecute().then(...) callback to handle the success case. This way:
  • both success and error cases are handled as close together (parsing and sending messages)
  • the loadAndExecute function returns the schema, and the parsing is done in the success handler
• I wrapped the .on calls with promises, similar to how it was done previously with the only listener used. Wrapping all of them with Promise.race will yield the first one to be resolved, being:
  • on('message'): if success or error is handled
  • on('error'): if error is not handled in the child process
  • on('close'): if process has ended by any other reason. This is just a fallback as it would be expected for the other listeners to be triggered first

[vercel[bot]]

@ochicf is attempting to deploy a commit to the Rico Kahler Team on Vercel.

A member of the Team first needs to authorize it.

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
sanity-codegen-dev	🔄 Building (Inspect)			May 10, 2023 2:29pm