file dependency's relative path resolution is different than npm's

[unbornchikken]

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

bug

What is the current behavior?

I have a local module that is referenced by path in my application's package.json, e.g:

"co-main": "file:../CompanyModules/base/co-main/"

That co-main module depends on another company module that is reside an other directory. So in co-main's package.json has this:

"co-utils": "file:../co-utils"

So, for the better understanding, the directory structure is the following:

C:
|- Dev
    |- MyCoolApplication (co-main referenced there)
    |- CompanyModules
        |- base
            |- co-main (here lies co-main that references utils with file:../co-utils)
            |- co-utils

npm install runs fine, but yarn install fails with the following:

error "C:\\Dev\\co-utils" doesn't exist.

So the bug is obvious, yarn resolves co-main's relative path by using the main package.json's path (C:\Dev\MyCoolApplication), but npm uses the submodule's root path for relative resolution (C:\Dev\CompanyModules\base\co-main).

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

1. Create an environment described above
2. Run npm install, it gets succeeded
3. Run yarn install, it gets failed with the above error

What is the expected behavior?

yarn resolves relative paths exactly like npm does.

Please mention your node.js, yarn and operating system version.

Windows 10, Node.js 4.6.0, yarn 0.15.1, npm 3.10.5

[leecade]

any plan to support this key feature?

[ozsay]

yarn/src/resolvers/exotics/file-resolver.js

Line 26 in ba5a203

loc = path.join(this.config.cwd, loc);

seems like the file resolver always resolves relative to cwd when the module path is not absolute. what it should do is resolve relative to the parent package (recursively).

looks like #1498 is solving this

[hpurmann]

Solved by #1498. I can confirm that this is fixed (macOS though). @kittens can you close?