Handle “Unsupported architecture” error better
This happens when nodecert is run on a platform that a mkcert binary has not been packaged for.
🆕 [Nodecert] Setting up… (node:9070) UnhandledPromiseRejectionWarning: Error: Unsupported architecture at mkcertBinaryForThisMachine (/email@example.com/nodecert/index.js:109:41) at module.exports (/firstname.lastname@example.org/nodecert/index.js:28:26) at Object.Greenlock.createServer (/usr/local/bin/node_modules/@small-tech/https/index.js:162:7) at Site.createServer (/usr/local/bin/index.js:399:18) at Site.endAppConfigurationAndCreateServer (/usr/local/bin/index.js:244:24) at new Site (/usr/local/bin/index.js:137:10) at /usr/local/bin/bin/commands/serve.js:164:24 at processTicksAndRejections (internal/process/task_queues.js:93:5) (node:9070) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1) (node:9070) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.