Add option for generating *named* module factories

_ I was blind, but now I see_

Hi, I'm profiling a RN app, and I'm looking into time it takes to do all the imports at app startup. Here's what the profiler could show me out of the box:

Nothing. I see minor clues here and there, but I don't know which files correspond to which boxes. Absolutely useless.

I made a very minor change to Metro to spit out Modules like so:

// (normally this function is anonymous)
__d(function ____app_components_TaskDetails_CommentsList_helpers_js(/* ... */) {

And now, the profiling experience is completely transformed:

I don't have a proper patch at this time, but it's literally a ~10LOC change: https://gist.github.com/radex/cc0e443f019bc0f94a76fcbd9200b48e

It would be quite trivial to add this to dev mode/profiling mode/under a flag, and if not — I'm making this post in case my contraption is useful to anyone else

Start with the linked ~10-line gist and trace Metro's module-factory generation path. Add an opt-in mode or flag that emits names derived from module paths, then verify that profiling output identifies the corresponding files without changing the default output.