Skip to content

support opts.package in non-relative lookups #152

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

Merged
merged 1 commit into from
Apr 4, 2018

Conversation

kellyselden
Copy link
Contributor

It looks like the non-relative lookup here was missed when adding the opts.package feature (which I would like to utilize).

Copy link
Member

@ljharb ljharb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, this seems like a straightforward bugfix that only impacts when opts.package is provided.

@ljharb ljharb merged commit c8a2052 into browserify:master Apr 4, 2018
@kellyselden kellyselden deleted the package branch April 5, 2018 18:18
ljharb added a commit that referenced this pull request Apr 7, 2018
 - [New] `resolve.sync`: add `opts.pathFilter` (#146)
 - [Fix] Make loadAsFileSync() work the same as async loadAsFile() (#146)
 - [Fix] support `opts.package` in non-relative lookups (#152)
 - [Docs] fix default “isFile” implementations
 - [Docs] fix options formatting
 - [Refactor] cache default isFile functions at module level
 - [Refactor] use "basedir" instead of "y", because meaningful variable names
 - [Tests] add some tests for a non-directory basedir (#154)
 - [Tests] work around npm SSL issue
 - [Tests] add some tests for browser field
 - [Tests] add node 8 and 9 to appveyor
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.

2 participants