You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently only the local package.json is copied into the build directory. Because the workspace global package.json (with it's resolutions fields) is missing package resolution behaves different to outside of leeway.
One way to "fix" this would be to add a config workspaceRootPackageJson and merge that into the local package.json.
Also @AlexTugarev discovered that the installer-package.json which we generate to install Typescript packages does not contain the resolutions from the package it installs. This seems to have the effect that yarn ignores the resolutions (at least in case they do not match the version patterns) which leads to different build results (breaking builds).
If the above is true there are two (closely related) tasks here:
Merge resolutions from the workspace root package.json into typescript packages
Copy resolutions from each Typescript package into it's installer-package.json
Currently only the local
package.json
is copied into the build directory. Because the workspace globalpackage.json
(with it'sresolutions
fields) is missing package resolution behaves different to outside of leeway.One way to "fix" this would be to add a config
workspaceRootPackageJson
and merge that into the localpackage.json
./cc @akosyakov
The text was updated successfully, but these errors were encountered: