-
-
Notifications
You must be signed in to change notification settings - Fork 185
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
Hidden StackOverflow issue (resulting in bug + perf) #125
Comments
stefanpenner
added a commit
to stefanpenner/node-resolve
that referenced
this issue
Apr 20, 2017
stefanpenner
added a commit
to emberjs/data
that referenced
this issue
Apr 20, 2017
…s about 800ms from ember-cli startup time) actual upstream issue: browserify/resolve#125 actual upstream PR: browserify/resolve#126 But we should upgrade anyways.
Wow, nice (try/)catch! |
stefanpenner
added a commit
to stefanpenner/node-resolve
that referenced
this issue
Apr 20, 2017
stefanpenner
added a commit
to stefanpenner/node-resolve
that referenced
this issue
Apr 20, 2017
stefanpenner
added a commit
to stefanpenner/node-resolve
that referenced
this issue
Apr 20, 2017
stefanpenner
added a commit
to stefanpenner/node-resolve
that referenced
this issue
Apr 20, 2017
I see what you did... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
resolve.sync
of a module with apackage.json
containingmain: '.'
will hang for quite some time, (up to 800ms on my machine) and then return return the correct value...Steps to reproduce:
If the
try/catch
is removed from https://github.com/substack/node-resolve/blob/master/lib/sync.js#L73 you instead get a fun stack overflowThe text was updated successfully, but these errors were encountered: