Invalid value type error keeps recurring and can't figure out why

[jcreamer898]

Do you want to request a feature or report a bug?
report a bug

What is the current behavior?
error An unexpected error occurred: "Invalid value type 7803:0 in /srv/core/js/yarn.lock".

If the current behavior is a bug, please provide the steps to reproduce.

Even after an rm -rf yarn.lock followed by a full yarn, running yarn again after that keeps getting the invalid value type error

What is the expected behavior?
I expect yarn install to work without an error on startup

Please mention your node.js, yarn and operating system version.
node v8.11.3, yarn 1.7.0, macOS

Here's the error stack trace and yarn.lock...
https://gist.github.com/jcreamer898/865c85b989c65412bb32bc7a4f7d2f35

[jcreamer898]

More information...

This error cropped up after I had a yarn.lock conflict. In the middle of a rebase I rm -rf yarn.lock and kept yarn-ing until the rebase was over.

So it's like this is only happening on a fresh yarn.lock.

[kylezeeuwen]

I accidentally added a random "Z" in the yarn.lock and got this exact error. The error pointed at line 51, but the Z was way down in the middle of the file. Checking for typos is a good first step if you get this error.

[kwelch]

This has been not from a rouge character from what I can tell. We are running yarn on a MBP and some are also running it within a Linux container. We are getting odd differences depending on where it is ran. Mainly, related to the resolved urls. There are cases where we get lock updates when we would not have expected to get them (aka no package.json change). Typically the lock file issue throwing invalid type does not display until the second install specifically after odd lock update.

Example:

-resolved "https://registry.yarnpkg.com/ajv-errors/-/ajv-errors-1.0.0.tgz#ecf021fa108fd17dfb5e6b383f2dd233e31ffc59"
+resolved ajv-errors/-/ajv-errors-1.0.0.tgz#ecf021fa108fd17dfb5e6b383f2dd233e31ffc59

Not really sure entirely on this, but my theory is that we are getting odd yarn differences between or containers and local machines. Is this something that foreseeably work, or are we operating in a false case.

One thing that I have found to work pretty consistently, if I can find a commit where we don't have a lock issue (on second install). Then reverting just the lock (git co -- yarn.lock) file to that commit and then running yarn it works.

Here is the error log I have from my last attempt.
https://gist.github.com/kwelch/6f85ffa439f3edc255ddc285a565abe0

[TooTallNate]

I am experiencing this as well. Is there any explanation?

[matthewdowns-eb]

I had this happen a few times. I was able to get it to start building a good yarn.lock again by checking out the latest from master:

git checkout origin/master -- yarn.lock
yarn install

[TooTallNate]

Thanks @matthewdowns-eb. That's more of a workaround though. I'm more interested in why it's happening.

[kwelch]

@TooTallNate, Are you running within docker containers? We have moved our solution out of containers and it start working again. That being said I don't believe we have had this issue recently (even within containers).

[jcreamer898]

We still see this every now and then... even in jest yarn 1.13.0.

updated 5/5/19 (duh)

[kwelch]

Yarn 1.13.0

[Shehryar-khan]

I had this happen a few times. I was able to get it to start building a good yarn.lock again by checking out the latest from master:

git checkout origin/master -- yarn.lock
yarn install

Well this worked for me after being stuck at it for two days.
Tried deleting the yarn.lock file and node_modules folder but it then gave alot of package errors when running the project.
Also tried changing the node version.
The solution which worked is this

Thanks for the solution.

[Alkhatri77]

Help my please

[Shehryar-khan]

Help my please

Are you still having the issue ?