Look for yarn.lock in parent directories

[k1sul1]

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

What is the current behavior?
When I run yarn add [package] while editing JS files inside app/js, I get the following output:

:!yarn add cookies-js # running from Vim

yarn add v0.24.4
info No lockfile found.
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Saved lockfile.
success Saved 1 new dependency.
└─ cookies-js@1.2.3
Done in 1.06s.

However, there already is a package.json, yarn.lock and node_modules in the project, just located in /.

What is the expected behavior?
Check if project already has a lockfile, and if it does, add the new dependency to that existing lockfile instead of generating a new lockfile and dependencies to the wrong directory.

package.json could have a "root" field similar to EditorConfig.

Please mention your node.js, yarn and operating system version.
Node: 7.7.2
Yarn: 0.24.4
OS: macOS Sierra 10.12.4

[bestander]

Yeah, I think Yarn should look for the closest package.json in that case.
Anyone wants to send a PR?

[BYK]

I think this is very similar to #2709 so shall we merge them?