#`trunk serve´ fails on M1 Mac

4 messages · Page 1 of 1 (latest)

steady herald
# 
trunk serve
2023-02-15T09:22:44.074568Z  INFO 📦 starting build
2023-02-15T09:22:44.075166Z  INFO spawning asset pipelines
2023-02-15T09:22:44.147711Z  INFO building frontend
2023-02-15T09:22:44.147739Z  INFO copying & hashing css path="public/main.css"
2023-02-15T09:22:44.148024Z  INFO finished copying & hashing css path="public/main.css"
    Finished dev [unoptimized + debuginfo] target(s) in 0.03s
2023-02-15T09:22:44.212133Z  INFO fetching cargo artifacts
2023-02-15T09:22:44.277676Z  INFO processing WASM for frontend
2023-02-15T09:22:44.287883Z  INFO calling wasm-bindgen for frontend
2023-02-15T09:22:44.288263Z ERROR ❌ error
error from HTML pipeline

Caused by:
    0: error from asset pipeline
    1: error spawning wasm-bindgen call
    2: Bad CPU type in executable (os error 86)
2023-02-15T09:22:44.288400Z  INFO 📡 serving static assets at -> /
2023-02-15T09:22:44.288453Z  INFO 📡 server listening at http://127.0.0.1:8080

I'm trying to get my tauri project up and running on an M1 Mac (works on an Intel Mac) but for some reason the trunk serve command fails as shown. I don't have rosetta 2 installed and would be interested in a solution without it if possible. The frontend folder builds successfully (it's Rust as well) and I have installed trunk, wasm-bindgen-cli and tauri-cli using cargo. wasm-bindgen --version works as well. I have the latest version installed of all of these things. How could I solve this issue? 🤔 Thank you very much in advance.

elfin plank
#

sounds like something the trunk/yew guys could help you better than us 🤔

There are a few issues about this here https://github.com/thedodd/trunk - some people say it was fixed in 0.16, some others say it wasn't. so ig there's more than 1 possible root cause.

Since you installed wasm-bindgen-cli you probably where aware of that stuff already right? (it was mentioned in some issues)

steady herald
#

I think I've always been installing wasm-bindgen-cli manually at the start, but yes, I found at least one issue where it was mentioned as well.

#

Thanks for the message though 👌 maybe I just have to do some more digging over there.