also, package.json files are just instructions on ...
# general
b
also, package.json files are just instructions on where to find things for installation, not runtime resolution, and i think even if you do the above and then make a bunch all your source modules’ package.json files point to those cached copies using symlinks or relative paths, it will still “install” them again by copying them into place under your package, defeating the point of installing them earlier and caching