This repository has been archived by the owner on Jul 3, 2019. It is now read-only.
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.
directory deps are a weird creature -- they require that npm actually go through some lifecycles and such. On top of that, npm/npm#15900 is changing the way directory deps work, to make them symlink.
This PR compromises by letting npm do the heavy lifting on this front. pacote will still be able to read local directory manifests for the CLI, but the CLI will have to do its own linking, do its own filtering so it doesn't ask pacote to extract a directory dep, and, if it wants to use pacote before the new behavior is out, pack its own tarball and then switch to local tarball mode for the rest of the process.