[BUG] npm link
does not work correctly with workspaces and install-strategy=nested
#7315
Open
2 tasks done
Labels
Is there an existing issue for this?
This issue exists in the latest npm version
Current Behavior
I have two projects
Puppeteer uses this .npmrc
install-strategy=nested
.packages/puppeteer-core
has thechromium-bidi
as a dependency.The linked package get linked at the top level rather then on the package-level.
That mean the downloaded version is always resolved by Node.
Expected Behavior
The linked packages is placed in the correct place
packages/puppeteer-core/
and runs the locally linked version.Steps To Reproduce
puppeteer
andchromium-bidi
npm run build
in both (will build anything necessary, also prevent's an issue related to linking andpeerDependencies
where there are type errors)npm link
inchromium-bidi
npm link chromium-bidi
ornpm link chromium-bidi -w puppeteer-core
inpuppeteer
packages/puppeteer-core/node_modules/chromium-bidi
is the downloaded version and not the symlink one.node_module/chromium-bidi
is a symlink tochromium-bidi
Environment
The text was updated successfully, but these errors were encountered: