packages are linked incorrectly on windows

[aaronabramov]

here's a repro build: https://ci.appveyor.com/project/Daniel15/jest/build/4207
PR: #4134

In the logs you can see that require.resolve('jest-config') returns :\projects\jest\node_modules\jest-config\build\index.js which seems to be the last published version of the package from npm.
locally and on circle/travis it resolves to jest/packages/jest-config/build/index.js, the local version of the file.

[thymikee]

Is it something we do wrong, or maybe a Lerna bug?

[cpojer]

cc @bestander

[bestander]

Will look at it today

…

On Thu, Jul 27, 2017 at 7:22 AM Christoph Nakazawa ***@***.***> wrote: cc @bestander <https://github.com/bestander> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#4135 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACBdWBci4FBih5922ZK5t8iS5mdjFvN_ks5sSJ0YgaJpZM4Okliw> .

[bestander]

@aaronabramov I don't have a windows PC at this moment.
I'll try to help diagnosing the problem if it is related to Yarn workspaces.

What does https://ci.appveyor.com/project/Daniel15/jest/build/4233 line 80-125 tell you?
This PR #4151.

[aaronabramov]

@bestander seems like yarn update fixed the issue. line 129 prints out the path to the local package directory (unlike mine PR where it goes to node_moduels)
i'll make sure next time i'll try updating yarn first :)
i made a PR with a small change in package APIs to make sure tests are still passing #4154 and the build seems to be green

[thymikee]

Reopening, we have two PRs hitting that

[cpojer]

This belongs on the Yarn issue tracker.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.