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

use same instance on symlinked modules #1318

Merged
1 commit merged into from Jul 9, 2015

Conversation

chrisirhc
Copy link
Contributor

Handle required packages by their real path.

Resolves #1063

Again, this is a request for further comment.

This isn't using a cache which might be faster (or not, since resolve might only be called for new packages encountered).

@chrisirhc
Copy link
Contributor Author

Updated PR. Tests now pass.

@ghost
Copy link

ghost commented Jul 9, 2015

Aside from the sync issue, this looks good. We should just make sure to not re-introduce this bug: #831

@ghost ghost merged commit 504832b into browserify:master Jul 9, 2015
@ghost
Copy link

ghost commented Jul 9, 2015

I added some tests for the case in #831 and everything works. Published in 10.2.5/10.2.6. Thanks for the patch!

@marcello3d
Copy link

(Edit: moved problem to new issue: #1325)

This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

Modules are executed multiple times when using symlinks in node_modules
2 participants