Ran cargo update on the workspace to get the latest deps according to the Cargo.toml file.
Upgraded tide to the latest version as a former bug with the newer Rust nightly builds was fixed in a newer build of tide.
SWC had some various changes that was done in src/swc_ops.rs and the SWC nodes seem to now react to the span field, so I threw in the DUMMY_SP which zeros the span out when doing the import_map rewrite.
The only issue at the moment is there is some hiccups where the JS side of Toast is throwing a RequestError: write EPIPE error which I am unsure if it is due to the way MacOS on ARM handles sockets changed or if the update to tide broke the socket.
Otherwise, I was able to confirm that both of the starters in https://github.com/toastdotdev/starters were able to build on Apple Silicon with these changes, so for the moment if there is no setDataForSlug or sourceData calls, a Toast site will properly build on the M1 Macs.
ChristopherBiscardi
commented
3 years ago
Changes
cargo updateon the workspace to get the latest deps according to the Cargo.toml file.tideto the latest version as a former bug with the newer Rust nightly builds was fixed in a newer build of tide.src/swc_ops.rsand the SWC nodes seem to now react to thespanfield, so I threw in theDUMMY_SPwhich zeros the span out when doing the import_map rewrite.The only issue at the moment is there is some hiccups where the JS side of Toast is throwing a
RequestError: write EPIPEerror which I am unsure if it is due to the way MacOS on ARM handles sockets changed or if the update totidebroke the socket.Otherwise, I was able to confirm that both of the starters in https://github.com/toastdotdev/starters were able to build on Apple Silicon with these changes, so for the moment if there is no
setDataForSlugorsourceDatacalls, a Toast site will properly build on the M1 Macs.