Native darwin/arm64 build via NPM

[theashguy]

💡 Feature request

Overview and problem statement

About to pick up Cloudflare / Wrangler as a core platform for a new project and just replaced my daily machine with a new M1 mac. Noticed that the npm install instructions don't work with the new platform.

When I try to install it I get Error: Unsupported platform: Darwin arm64.

Basic example

Just do the old npm install wrangler-cli -g

Workaround

Works fine if you use cargo to build directly for the env. Just make sure you remove the one installed by npm else you might get a clash of binaries :). It might be worth updating the documentation somewhere to point to this for the time being :).

[tillkruss]

Just tried to install wrangler using NPM on an M1 machine and got the same error.

Manual install doesn't work either.

[cpauwels]

Same issue here, with wrangler being one of the only things holding me back to working 100% with my M1 Mac.

I installed rust via arm64 homebrew, and then used cargo to install wrangler. Everything compiled successfully, but when trying to run wrangler I get the following error:

  throw new Error(`Unsupported platform: ${type} ${arch}`);
  ^

Error: Unsupported platform: Darwin arm64
    at getPlatform (/Users/capauwels/.nvm/versions/node/v15.3.0/lib/node_modules/@cloudflare/wrangler/binary.js:19:9)
    at getBinary (/Users/capauwels/.nvm/versions/node/v15.3.0/lib/node_modules/@cloudflare/wrangler/binary.js:30:20)
    at run (/Users/capauwels/.nvm/versions/node/v15.3.0/lib/node_modules/@cloudflare/wrangler/binary.js:38:18)
    at Object.<anonymous> (/Users/capauwels/.nvm/versions/node/v15.3.0/lib/node_modules/@cloudflare/wrangler/run-wrangler.js:4:1)
    at Module._compile (node:internal/modules/cjs/loader:1102:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1131:10)
    at Module.load (node:internal/modules/cjs/loader:967:32)
    at Function.Module._load (node:internal/modules/cjs/loader:807:14)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:76:12)
    at node:internal/main/run_main_module:17:47

Any idea on when there will be support for M1 macs?

[xtuc]

We don't have plans to work on M1 compatibility. However I think that's something wrangler needs to support.
The build configuration is here https://github.com/cloudflare/wrangler/blob/master/.github/workflows/release.yml#L71. Do you know if GitHub actions run M1 macs?

[tillkruss]

They do not. We rented an M1 at MacStadium for testing. Cross-compiling works from Intel => ARM.

[yongfook]

@cpauwels looks like you need to remove the non-functioning npm version so the system can use the cargo binary.

Try running

npm uninstall -g @cloudflare/wrangler

And then try the wrangler command again.

[theashguy]

Can confirm that Cargo version does work-- sorry, should have come back to report on this. That said there are a range of other problems that you need to workaround. Ultimately I'm now using a custom webpack config to actually do the build and just using wrangler for deploys.

So yes you can dev CFF on an M1, but wrangler is not M1 ready (actually one of the few things I've found that isn't), so be ready to fiddle with things.

To be clear the problems with M1 install aren't really problems with any of the software working on the chip-- everything in the stack compiles just fine. There are just jaggy edges in the configuration and baked in assumptions across the tooling where it relies on pre-built binaries to be installed in certain ways or whatever that ultimately cause the issues. I suspect if you can find someone on the ground who can lend you an M1 mac for a few hours you could shake them out (ie, always allow falling back to custom build, or even to BYO binaries for the components it calls out to) and there wouldn't be any issues going forward.

[nilslice]

I've seen a similar issue:

wrangler publish    
⬇️   Installing wasm-pack v0.9.1...
Error: could not download `wasm-pack`
no prebuilt wasm-pack binaries are available for this platform

Which could potentially be that wrangler is a bit overeager in its convenience-added approach. Rather than expect to download a pre-built binary and fail otherwise, it could first check for an existing binary on the system, and fall back to attempting to download. Or, if cargo is installed, cargo install <wasm-pack|generate|etc> could be invoked to build these utils from source.

I've manually installed wasm-pack, cargo-generate and at least one other tool that doesn't have native pre-built binaries for M1 devices. So it should be fine, if not a little bit less "controlled", to first check for the binary before attempting to download one.

---

update:

// src/install/dependencies.rs

pub const WASM_PACK_VERSION: &str = "0.9.1";
pub const GENERATE_VERSION: &str = "0.5.0";

If these versions are required for compatibility, then it makes much more sense why wrangler is attempting to install these in particular.

[nilslice]

in-progress PR to address part of this issue: #1763

[paulosouzainfo]

in my case was install using homebrew with success!
brew install cloudflare-wrangler

[yongfook]

in my case was install using homebrew with success!
brew install cloudflare-wrangler

Installing cloudflare-wrangler is not a problem for me.

But it fails when attempting to run subsequent commands that depend on cargo-generate.

wrangler generate my-worker                 
⬇️ Installing cargo-generate v0.5.0...
Error: could not download `cargo-generate`
no prebuilt cargo-generate binaries are available for this platform