berry: [Bug] Not running simple yarn install

FWIW the quickest fix if you can’t find the offending yarn.lock file is to simply touch yarn.lock from the folder you’re trying to run your other yarn commands from.

Do you by any chance have a yarn.lock in /app? The error message doesn’t reference the cloned project, which leads me to believe that Yarn thinks /app is the root of your app. This should only happen if you have a lockfile in an ancestor folder.

got working here

there are a yarn.lock there on home dir as well

FWIW, I could reproduce. I had unused yarn.lock files in two ancestor files. Deleting them fixed it for me.

~/yarn.lock
~/Projects/yarn.lock

Can we reopen this in order to improve the error or the behavior of yarn?

Maybe the error message could be clearer. Something like:

Usage Error: A yarn.lock file was found in a higher directory ({path}), but it doesn't seem to have been installed. Either run an install there, or delete the file.

Or perhaps yarn should not regard stray yarn.lock files in ancestor directories. Is this a valid use case with yarn? Should yarn stop at the first package.json it finds when searching upward in the directory tree?

In my case, I ran yarn from a directory with a package.json, but my home directory had a yarn.lock but no package.json. I’m not familiar with yarn 2, and I admit I didn’t fully read the file path in the error message. I was running a storybook setup command (npx sb@next repro) as you can see in the above linked issue. So this caused confusion for me.

After yarn set version latest the error was more detailed. I needed to remove ~/package.json.

I encountered this error also with yarn3 and found some yarn.lock files and package.json files outside of the projectdir, but removing them didn’t resolve the issue

@willgriffiths Just a heads up, I had a package.json randomly in my User directory that was also causing me the same issue in ~/dev/projectdir.

I can confirm, I had the same issue and removing yarn.lock and package.json files from root directory solved the issue for me on fedora linux. yarn version 3.1.1

I have a file named package.json file in a distant parent directory that is completely unrelated to the project I am currently working on. It is frustrating beyond relief that I have to rename it just so that yarn thinks $(pwd)/package.json is the root of a workspace; and I cannot find any means to tell it explicitly so.

eslint has a root: true option, which tells it not to scan up the directory tree any further. Does yarn have a similar .yarnrc.yml option?

the problem now is that there are no package.json there to be excluded

Sorry if I’m making you repeat yourself but did you also remove a yarn.lock from the home dir? /Users/sibelius/yarn.lock

Yarn 2 supports nested workspaces which may relate to the change in behaviour. arcanis would know more.

@willgriffiths Just a heads up, I had a package.json randomly in my User directory that was also causing me the same issue in ~/dev/projectdir.

Thanks for creating an issue @sibelius. I added a feature request based on your feedback.

Let us know if you hit any other blockers with yarn 2. 😃