Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

install: improve isOnly(Dev,Optional) #206

Closed
wants to merge 1 commit into from

Conversation

larsgw
Copy link
Contributor

@larsgw larsgw commented Jul 1, 2019

Instead of creating a new set each time a new node gets visited, so that
its siblings do not have it in seen, just remove the node from the
original set right after all child nodes are visited.

See #76

Instead of creating a new set each time a new node gets visited, so that 
its siblings do not have it in `seen`, just remove the node from the 
original set right after all child nodes are visited.

See npm#76
@larsgw larsgw requested a review from a team as a code owner July 1, 2019 23:52
@isaacs isaacs added the semver:patch semver patch level for changes label Jul 2, 2019
@isaacs
Copy link
Contributor

isaacs commented Jul 2, 2019

This will be in 6.10.1. Thanks!

isaacs pushed a commit that referenced this pull request Jul 2, 2019
Instead of creating a new set each time a new node gets visited, so that
its siblings do not have it in `seen`, just remove the node from the
original set right after all child nodes are visited.

See #76

Credit: @larsgw

PR-URL: #206
Close: #206
Reviewed-by: @isaacs
isaacs pushed a commit that referenced this pull request Jul 3, 2019
Instead of creating a new set each time a new node gets visited, so that
its siblings do not have it in `seen`, just remove the node from the
original set right after all child nodes are visited.

See #76

Credit: @larsgw

PR-URL: #206
Close: #206
Reviewed-by: @isaacs
@DanielRuf
Copy link

I guess we can close this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
semver:patch semver patch level for changes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants