-
Notifications
You must be signed in to change notification settings - Fork 412
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
if target/wasm-bindgen already exists don't attempt to re-add/install it #51
Comments
I would love to help out with this one if it wouldn't be too difficult for a first contribution! Would you have any advice for identifying whether or not target/wasm-bindgen exists already? I'm guessing that this would mean adding a check to the |
hey @data-pup ! so, i wasn't actually entirely sure- this stack overflow answer seems mostly reasonable: https://stackoverflow.com/questions/35045996/check-if-a-command-is-in-path-executable-as-process. lemme know if you need help digesting it! |
Hi! Thank you for the link, that definitely helped. I started working on this today, here is the branch with some first steps. I think I will need to add some extra logic for this to work on Windows, which uses Should the progress bar still show up if wasm-bindgen is already installed? Right now it just exits the |
hey @data-pup ! sorry for the delay, i was out sick earlier this week- do you think you could open up a PR? it's much easier to give feedback :D looking forward to reviewing it and thanks so much! |
Hi @ashleygwilliams! Sure thing, I can open a PR today. Thanks for helping me out with contributing, I really appreciate it and am looking forward to helping out more! |
@data-pup can you run |
@ashleygwilliams Here are the versions of rustc and rust-fmt. These might be slightly out of date, I can update these and see if that fixes the issue.
Update: I updated my nightly toolchain, and formatted using these versions:
This did not seem to fix the problem. The Travis build failed again :/ |
Fixed in #192 |
No description provided.
The text was updated successfully, but these errors were encountered: