Local workspace dependencies are present among node_modules, but they're, ahm, weird
When using nodeLinker: node-modules
, the local packages of the workspace(i.e. resolved by workspace:path/to/package
, not deployed to a registry) are not unpacked(sort of) during the yarn install. They are just simple files(not folders, not zips) with the name of the package, and nothing in it(they're about 100 bytes in size). We're using scoped packages if that is relevant to this.
The console also logs the following: @my-scope/my-package@workspace:sub-directory/my-package can't be found in the cache and will be packed from disk
The .yarn/cache
looks good, all local packages look good, they have been packed correctly, it's only the install phase which populates the node_modules folder that's wrong. In case it helps, the zips are named as @my-scope-my-package-workspace-3a9e8f551c-7.zip
. That workspace
in the name of the zip is what could be causing the issue, and yarn doesn't understand that kind of resolution. Also, checking the yarn.lock
, it's still specifying the resolution as workspace:path/to/package
.