When I was missing this feature, I was thinking of something like splitting off the directory of the result of Base.find_package, or equivalently Base.pathof without loading the module.
But now that I have used 1.0 a bit more, I don’t miss Pkg.dir that much. I think that removing it was the right decision, since it served as a basis for various other use cases, all of which have better solutions. Namely,
- testing, coverage, and docs generation in
.travis.ymland other CI servises (solution: no need to have the directory directly, and one can always use projects), - locating files relative to source (solution: use
@__DIR__as a basis for this, ideally via a function), - just want to browse the files, eg for reading the source (solution:
import, thenpathof, orpkg> devfor editing as suggested above).