New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't run wrker-build, assumes ~/.cargo/bin is in PATH and fails otherwise #45
Comments
Hey @tv42 - thanks for reporting this. If you're already using Rust, you're probably using You're welcome to run your own build script in place of the one placed in the template though! Happy to consider any suggestions to work around your 2 ideals above. |
Is the issue with PATH being used just that you didn't have your PATH set after installing Rust via something like |
@tv42 - I transferred this issue to the |
I didn't use rustup to install rust, and consider having randomly named things from random projects at random versions in my $PATH both a usability, reproducability, and security problem. But I'm not going to bother trying to change your mind. |
馃悰 Bug report
Describe the bug
This is just developer friction / newbie trap.
Wrangler 1.19.2 installed by building via cargo.
Reproduce the bug
With the template Rust workers demo from https://blog.cloudflare.com/workers-rust-sdk/
Expected behavior
Ideally:
Environment and versions
Fill out the following information about your environment.
wrangler -V
: wrangler 1.19.2node -v
: node: command not foundwrangler.toml
: unedited from templateThe text was updated successfully, but these errors were encountered: