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

Adds support for "paths" being a function #172

Merged
merged 0 commits into from
Nov 22, 2018
Merged

Conversation

arcanis
Copy link
Contributor

@arcanis arcanis commented Nov 14, 2018

Split out of #170.

This PR adds support for the paths option being a function. This allows to dynamically compute the lookup paths based on the path being requested and the issuer making the request.

lib/async.js Outdated Show resolved Hide resolved
lib/sync.js Outdated Show resolved Hide resolved
@ljharb ljharb force-pushed the paths=fn branch 2 times, most recently from 15acb75 to d5dc919 Compare November 22, 2018 02:02
@ljharb ljharb merged commit d5dc919 into browserify:master Nov 22, 2018
@arcanis
Copy link
Contributor Author

arcanis commented Dec 11, 2018

@ljharb By any chance, do you have an ETA for the next release?

@ljharb
Copy link
Member

ljharb commented Dec 13, 2018

@arcanis i've got a branch ready, but there's two bugfixes I'm trying to get fixed first. Hopefully within the next week!

ljharb added a commit that referenced this pull request Dec 17, 2018
 - [New] `async`/`sync`/`node-modules-paths`: Adds support for “paths” being a function (#172, #173)
 - [New] Implements a "normalize-options" pseudo-hook (#174)
 - [Fix] `sync`/`async`: fix `preserveSymlinks` option (#177)
 - [Fix] `sync`/`async`: when package.json `main` is not a string, throw an error (#178)
 - [Deps] update `path-parse`
 - [Dev Deps] update `eslint`, `@ljharb/eslint-config`, `object-keys`, `safe-publish-latest`, `tape`
 - [Tests] up to `node` `v11.4`, `v10.14`, `v8.14`, `v6.15`
 - [Tests] better failure messages
@ljharb ljharb mentioned this pull request Jan 5, 2020
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