-
Notifications
You must be signed in to change notification settings - Fork 68
resolve updates #56
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
Comments
Upgrading appears to breaks one of the browser-resolve tests. I'll iterate on resolve to see if I can get everything to pass. |
All fixed in 1.1.4. I also noticed in the current browser-resolve implementation that a package.json of: {
"browser": {
"xyz": "wow.js"
}
} does not work for {
"browser": {
"./xyz": "wow.js"
}
} This is because internally a |
Just published under 1.7.1. The only change was upgrading resolve to 1.1.4. |
I just fixed some very tricky issues in resolve that were cropping up in browserify and are now part of the test suite. I recommend upgrading to 1.1.3, since the current tests fail when browser-resolve uses the old version.
The updates address some errors with the previous
opts.pathFilter
implementation and some very subtle bugs when there is a./file.js
and a./file
directory.The text was updated successfully, but these errors were encountered: