install script in scoped package referencing linked workspace package fails on Windows

[artursgirons]

Bug report

• yarn 1.13.0
• Node 10.15.0
• Windows 10 1809 (BUG)
• macOS Mojave 10.14.2 (SUCCESS)

Workspace definition:

  "workspaces": {
    "packages": [
      "platforms/*/packages/*",
      "platforms/*",
      "projects/*",
      "templates/template-project"
    ]
  }

Install script in packages:

  "scripts": {
    "install": "frontful-tools install",
  },

When I have a scoped @template/platform package in platforms/* that calls postinstall install script that is linked in workspace, and I do yarn install I get an error:

Cannot find module 'C:\workspace\node_modules\node_modules\frontful-tools\bin\frontful-tools.js'

NOTICE: \node_modules\node_modules\

When this package (frontful-tools) is present in any of @template\platform's packages/* I get simmilar but different error:

Cannot find module 'C:\workspace\node_modules\@template\platform\packages\frontful-tools\bin\frontful-tools.js'

NOTICE: \node_modules\@template\platform\packages\

All of these things work on macOS as expected, no errors, all scripts get launched as expected.

Simple steps to reproduce on Windows:

• git clone https://github.com/frontful/frontful-workspace
• copy templates/template-platform to platforms/template-platform
• yarn install

If I remove @template/platform scope all works as expected.

[artursgirons]

What I ended up doing is to remove the scope from intermediate projects (those in platforms/* workspace definition above) as those projects won't be published anyway they are just monorepos with some utilities to manage all the packages in platforms/*/packages/*. But still, it would be nice if when scoped install script won't cause the error on Windows.