This repository has been archived by the owner on Jan 7, 2022. It is now read-only.
Fixes error handling to create a Node Object when a child package is not exist #6
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
watilde
force-pushed
the
patch/fixes-error-handling
branch
from
905ee6f to
c38df2d
Compare
watilde
force-pushed
the
patch/fixes-error-handling
branch
from
c38df2d to
32f9202
Compare
|
@iarna Hi Rebecca, could you please see this for a issue is tagger |
watilde
force-pushed
the
patch/fixes-error-handling
branch
from
32f9202 to
1592a19
Compare
|
@watilde Oooh, I just ran across this, I wish I'd been looking in these PRs earlier!! I fully expect this to solve a whole class of ENOENT errors. Thank you for putting this together, I'm gonna get it merged ASAP. |
|
Released as 5.1.5! |
iarna
added a commit
to npm/npm
that referenced
this pull request
Jun 24, 2016
Make bad symlinks be non-fatal errors when reading the tree off disk. Credit: @watilde Reviewed-By: @iarna PR-URL: npm/read-package-tree#6
4 tasks
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
refs: npm/npm#10201 (comment)
Updates