Fix for #318
Make module.parent available.
This is very confusing. The wrapper/ stuff isn't even in v2 anymore since all of this is handled by browser-pack now.
support module.parent; based on substack/node-browserify#323
It would certainly be nice to have the complete module spec available, eg loaded, parent, and children.
I haven't yet done so for node, but for ancient module runtimes I've written in the past, I've made use of this information to do some visualization.
There is also a similar, but slightly different "tree" shape available, at the you run browserify. Would be nice to have that tree available as well, presumably in a separate JSON file:
"children": ["bar", "baz"]
@pmuellr: module.children support is really easy (michaelficarra/commonjs-everywhere@5179659), especially after you support module.parent (michaelficarra/commonjs-everywhere@d90a6b3).
This should be implemented as a separate browser-pack module.
Now in 3.7.0 you can specify a custom opts.pack to browserify() so using a custom browser-pack implementation for this is much more feasible.