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
Apply transforms correctly to whole packages and modules that depend on multiple packages. #14
Conversation
I pulled this patch and am using your branch of
|
Hmm, and you've got node-resolve with the patches applied underneath that right? Had all tests passing before submitting the PR. Away from my computer now, but I'll reverify when I'm back. Sent from my iPhone On Jun 8, 2013, at 6:14 PM, James Halliday notifications@github.com wrote:
|
The problem was just that resolve depended on |
Nevermind, I just cloned it myself. The new fixes are published as module-deps@0.10.2 |
This patch removed |
What are the failures? I've got all browserify tests passing. Make sure you pull in the PR for browserify itself. Sent from my iPhone On Jun 8, 2013, at 8:25 PM, James Halliday notifications@github.com wrote:
|
I added back |
Whoops. Good catch. |
This patch fixes the following two issues:
#7
#13
This depends on the following pull requests in dependencies of
module-deps
:browserify/resolve#21
browserify/browser-resolve#23
Once in place, package metadata is preserved throughout the resolution process, allowing transforms to be applied correctly to whole modules (as well as addressing an issue of where transforms from multiple dependencies were not respected).