Adding 'install with yarn' to troubleshooting #367
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Hi, Just finished a two-hour session trying to figure out why Reason CLI tools won't install. Apparently it choked on a path which it thought `is too deep inside filesystem, Esy won't be able to relocate binaries`. This specific error was also silent, so I had to go into the esyBuildRelease shell script and make it spit it out. This [issue](reasonml/reason-cli#45) hinted using Yarn would do off with all that, and it did, installing quickly and happily. Might also be worth recommending Yarn as a default running for installing over npm, but I will leave that to more knowledgeable documentation editor.
|
cc @andreypopp |
|
I'm not sure that yarn would alway solve this issue — for me it looks like it just happened that yarn installs into a fs location which isn't so deep as the one used by npm. The issue with swallowing the actual error is the real one — I've pushed a fix into esy/esy#182. |
|
Thanks. I can confirm that the difference is where Yarn installs vs npm. But since the documentation states "if this doesn't work, try X, and if not, try Y, ..." and so on, this becomes just another solution to try. |
|
I think this pull request can be closed as |
|
You're right. Sorry for not merging this earlier and thanks again for the contribution @jondot. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
Just finished a two-hour session trying to figure out why Reason CLI tools won't install.
Apparently it choked on a path which it thought
is too deep inside filesystem, Esy won't be able to relocate binaries.This specific error was also silent, so I had to go into the esyBuildRelease shell script and make it spit it out.
This issue hinted using Yarn would do off with all that, and it did, installing quickly and happily.
Might also be worth recommending Yarn as a default running for installing over npm, but I will leave that to more knowledgeable documentation editor.