Creating a fresh site with an Atlas Addon frontend fails to spin up node app with Next 12

[blakewilson]

When creating a new site with the Atlas Local Addon, the frontend fails to spin up:

ready - started server on 0.0.0.0:10040, url: http://localhost:10040
info  - Loaded env from /Users/blakewilson/Local Sites/atlasfaustsite/app-node/.env.local
info  - Attempted to load @next/swc-darwin-x64, but an error occurred: dlopen(/Users/blakewilson/Local Sites/atlasfaustsite/app-node/node_modules/@next/swc-darwin-x64/next-swc.darwin-x64.node, 0x0001): tried: '/Users/blakewilson/Local Sites/atlasfaustsite/app-node/node_modules/@next/swc-darwin-x64/next-swc.darwin-x64.node' (code signature in <FFA6246B-5761-3AD5-AB55-34832928B990> '/Users/blakewilson/Local Sites/atlasfaustsite/app-node/node_modules/@next/swc-darwin-x64/next-swc.darwin-x64.node' not valid for use in process: mapped file has no cdhash, completely unsigned? Code has to be at least ad-hoc signed.), '/usr/lib/next-swc.darwin-x64.node' (no such file)
error - Failed to load SWC binary for darwin/x64, see more info here: https://nextjs.org/docs/messages/failed-loading-swc

This is because the Faust example recently started using Next 12, which uses a Rust based compiled with SWC instead of Babel. SWC requires a binary to be downloaded that is compatible with your system:

SWC requires a binary be downloaded that is compatible specific to your system. In some cases this binary may fail to load either from failing to download or an incompatibility with your architecture.

Here is Next.js' docs on this issue:
https://nextjs.org/docs/messages/failed-loading-swc

This is causing all node frontends created with the Atlas Local Addon to fail to spin up.