You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I found a few issues when I tried to follow the steps to build on a mac m1.
First of all, installing node 14 via npm is not possible per current configuration. Because it tries to download the node binary from node-bin-darwin-arm64 which unfortunately does not provide a build for node v14 but only v16+.
I can workaround that by using nvm to set my node version to v14 and change the shebang in ./tools/ceramic. But I think it is better to use node v16+ because v14 LTS is ending in a few months (Apr 2023). However, that leads to another problem: node-fibers does not support node v16+ (see its readme). So I'm afraid we will have to get rid of fibers in the long run.
Next problem is the sharp npm package, only starting from v0.29 it does provide a mac arm64 binary. I think this one is relatively easy to update.
The text was updated successfully, but these errors were encountered:
Ceramic is still using node 14 because of fibers yes. I'd like to migrate the fibers code eventually so that we can move to node 16, but that requires a lot of changes in the tools that I can't do right now.
Meanwhile, running Ceramic via Rosetta should work just fine (that's what I'm doing on my M1 mac at the moment).
I found a few issues when I tried to follow the steps to build on a mac m1.
First of all, installing node 14 via npm is not possible per current configuration. Because it tries to download the node binary from node-bin-darwin-arm64 which unfortunately does not provide a build for node v14 but only v16+.
I can workaround that by using nvm to set my node version to v14 and change the shebang in
./tools/ceramic
. But I think it is better to use node v16+ because v14 LTS is ending in a few months (Apr 2023). However, that leads to another problem: node-fibers does not support node v16+ (see its readme). So I'm afraid we will have to get rid of fibers in the long run.Next problem is the
sharp
npm package, only starting from v0.29 it does provide a mac arm64 binary. I think this one is relatively easy to update.The text was updated successfully, but these errors were encountered: