This is a issue to discuss whether the custom path argument can be removed to simplify the interface for this package.
Previously this was introduced to get around some issues with Yarn (99x#22). However, I think these are now resolved and I'm wondering whether there is still an overriding reason to keep this option given the additional complexity it adds both to this package and wrappers of this package.
If this is removed, it'll be considered a breaking change and only done in a new major version of this package.