Repository navigation
Support "resolutions" in typescript libraries #12
Description
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.
/cc @akosyakov
Reacted by Anton Kosyakov
Activity
geropl commentedon Sep 2, 2020
Also @AlexTugarev discovered that the
installer-package.jsonwhich we generate to install Typescript packages does not contain the resolutions from the package it installs. This seems to have the effect thatyarnignores 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:
resolutionsfrom the workspace rootpackage.jsonintotypescriptpackagesresolutionsfrom each Typescript package into it'sinstaller-package.json