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
Installation Problem: .yarn-metadata.json: Unexpected end of JSON input #660
Comments
Also seeing this:
|
We hit this at Exponent after getting a prior installation error due to a bad hash in the yarn.lock file. Current hypothesis is that a bad hash or other installation error causes Yarn to bail out and not properly clean up .yarn-metadata.json files. |
I triggered this condition after a failed install of
If you trigger this, you can workaround the issue with:
Then try your install again. In my case, the re-try worked. |
We were getting this on yarn 0.22 (installed via npm). We resolved it by upgrading to yarn 0.23.1 (installed via apt) and then running |
Should be fixed now |
Set the problem with the command "native command-inactive " |
Command failed: yarn add react-navigation@1.0.0-beta.11 i got this error while running ignite new FirstApp |
anyone to help me??? |
@Musigwa, looks like your cache might be corrupt. |
thank you i'm going to try it out |
Thanks at all it worked fine
…On Mon, Mar 5, 2018, 19:39 Konstantin Raev ***@***.***> wrote:
@Musigwa <https://github.com/musigwa>, looks like your cache might be
corrupt.
Try running yarn cache clean and then install again
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#660 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AcnBQGaZ3iQ6JH6DPfRObZLqVzuOu5wOks5tbXg1gaJpZM4KT5XQ>
.
|
thx |
This might help someone...perhaps, I might be needing it in the future. I was having this issue while trying to work on a project that required using
Problem: Corrupt cache Source: @bestander |
Don't forget that if you get this error on windows it can be because you have an empty package.json in your home directory (C:\Users\yourlogin\package.json). If you have the empty file there just delete it and you are on track again. |
You really saved my life! I tried all possible things and hunderts of reinstalls... :-) |
Thank you! This also solved my problem with yarn! |
I'm running the yarn install procedure within a Dockerfile, there's no cache. It's retrieving the dependencies directly from a registry. Why is this still a thing? Also I have seen this issue with |
thanks, |
In Windows first stop the development server and then try to install package. |
If you are unable to run |
Seems that yarn is creating a json file without contents and perhaps should be
{}
.The text was updated successfully, but these errors were encountered: