feat: add possibility to get modules

[fyodorovandrei]

What's the problem this PR addresses?
I needed to access the static modules multiple times. As shown in the links, people require them.

https://github.com/module-federation/universe/blob/main/packages/storybook-addon/src/lib/storybook-addon.ts#L81
https://github.com/nuxt-modules/storybook/blob/95cd445eed0cdc570bbfba03ff9589c727a41ee8/src/webpack.ts#L32C99-L32C99
...

How did you fix it?
A new method has been added to retrieve static modules.
...

[larixer]

getModules is a confusing API. How should I know as a developer that it returns only static modules and not both static and dynamic?

[larixer]

I'd prefer to have an API like getModuleList(options?: enum {ALL | STATIC | DYNAMIC}) and getModule(name: string) and the implementation would use _staticModules and finalInputFileSystem._virtualFiles to determine the module type and its contents. I'm not sure if you are willing to contribute that. It's more effort, but will result in a more roboust solution IMO.

[larixer]

Maybe it's okay to not distinguish between static and dynamic modules and return all module paths, i.e. have getModuleList() without options. But returning only static modules feels confusing for sure

[fyodorovandrei]

@larixer Could you please provide me with your feedback on whether I have extracted the dynamic modules correctly? Thank you.

[larixer]

@fyodorovandrei Many thanks, looks good!

[larixer]

@fyodorovandrei Published as webpack-virtual-modules@0.6.0

[fyodorovandrei]

Nice! Thank you @larixer