fix(plugin-pnpm) Pnpm linker avoids symlink loops on the file system #4542
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What's the problem this PR addresses?
Fixes #4525
How did you fix it?
Symlinks for dependencies are created higher in the directory structure. Instead of
<project_root>/node_modules/.store/webpack-cli-virtual-66f7aceb77/node_modules/webpack-cli/node_modules/commander
,the symlink is created at:
<project_root>/node_modules/.store/webpack-cli-virtual-66f7aceb77/node_modules/commander
This is the same way as
pnpm
does. This avoids the symlink loop on the file system. It works, because Node.js fallbacks torealpath
and parent directories look up when it fails to find a module without applyingrealpath
.Checklist