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
{{ message }}
This repository was archived by the owner on Aug 3, 2023. It is now read-only.
After going through a bit of pain trying to get nvm setup to install wrangler I explored a few alternative installation paths. My issues with nvm were my own user error but I eventually gave up and used rustup instead due to the confusing documentation around nvm. This repo points people to nvm as the first way to install wrangler, and I think this could lead to some developers (especially new developers) getting frustrated and moving on to other platforms because they can't even get started with the base config.
Switching to installing with brew and rustup worked and was pretty easy to do but still required messing around with PATH and env variables. This install setup is also slightly customized for M1 by switching the target to x86_64-apple-darwin. All of that makes it still a bit trickier then it should/could be for developers wanting to try out CF Workers for the first time. It also isn't very well documented that this can be achieved with brew at all.
@alexanderson1993 then tipped me off to Volta.sh which ended up being by far the easiest way to get setup compared to nvm and rustup. You can see an explanation of all three installation methods and how they compare here.
This has been discussed in a few previousissues which can be found by dedicated Googler's, but adding this info to the README or at least the Wrangler Install docs would be really useful. Most people will start at the beginning of the README and follow whatever instructions are given, which is why I try to always make the first path the simplest one.
The text was updated successfully, but these errors were encountered:
I like the simplicity of downloading a binary from https://github.com/cloudflare/wrangler/releases/latest, and moving it into a directory on my path. For a specific version (e.g. for durable object support), that method is probably the first choice.
Manual installation is menitioned in the docs. Perhaps adding a similar note in the README would help also.
💡 Feature request
After going through a bit of pain trying to get
nvm
setup to installwrangler
I explored a few alternative installation paths. My issues withnvm
were my own user error but I eventually gave up and usedrustup
instead due to the confusing documentation aroundnvm
. This repo points people tonvm
as the first way to install wrangler, and I think this could lead to some developers (especially new developers) getting frustrated and moving on to other platforms because they can't even get started with the base config.Switching to installing with
brew
andrustup
worked and was pretty easy to do but still required messing around with PATH and env variables. This install setup is also slightly customized for M1 by switching the target tox86_64-apple-darwin
. All of that makes it still a bit trickier then it should/could be for developers wanting to try out CF Workers for the first time. It also isn't very well documented that this can be achieved withbrew
at all.@alexanderson1993 then tipped me off to Volta.sh which ended up being by far the easiest way to get setup compared to
nvm
andrustup
. You can see an explanation of all three installation methods and how they compare here.Describe the feature
1. Install with
volta
curl https://get.volta.sh | zsh volta install node npm install -g @cloudflare/wrangler
2. Install with
brew
andrustup
3. Install with
nvm
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.38.0/install.sh | zsh touch .zshrc
Add the following script to
.zshrc
.Install the current Node LTS and then
wrangler
.Describe the alternatives
This has been discussed in a few previous issues which can be found by dedicated Googler's, but adding this info to the README or at least the Wrangler Install docs would be really useful. Most people will start at the beginning of the README and follow whatever instructions are given, which is why I try to always make the first path the simplest one.
The text was updated successfully, but these errors were encountered: