feat: enhance type capabilities

[2heal1]

Description

• support types hot reload
• support re-export remote types
• support consume/generate runtime api types
• support extract third parth types

demo start steps:

1. install deps

pnpm i 

2. build needed packages

nx build

3. start demos

pnpm app:ts:dev

You will see react-ts-host will auto fetch its remote types

And react_ts_nested_remote's dep react_ts_remote will be stored in react_ts_nested_remote's/node_modules which can support re-export remote .

when update the react_ts_nested_remote , the host will auto fetch the latest types :

Related Issue

#2154

Types of changes

• Docs change / refactoring / dependency upgrade
• Bug fix (non-breaking change which fixes an issue)
• [x ] New feature (non-breaking change which adds functionality)

Checklist

• I have added tests to cover my changes.
• All new and existing tests passed.
• I have updated the documentation.

[zackarychapple]

Would be helpful to know roughly what the dev server is doing.

[2heal1]

Would be helpful to know roughly what the dev server is doing.

I forget to add the rfc link , here is : #2154

And more details will be added soon

[ilteoood]

But for rspack/webpack , the reason why i specially process it is because i need to emit the dist(@mf-types.zip) to bundler assets , which can work on most bundler assets analyzer plugin.

Can you argue a bit about this? Sorry I didn't get what you mean

The plugin should emit the extra asset(@mf-types.zip) to the compiler self filesystem, because most plugin will use compilation.getAssets() to process the assets , such as webpack-manifest-plugin.

Got it. But to do so, IMO you don't need any of this code. As I said, using the bundler's proxy and a simple server would be enough and also bundler agnostic

[2heal1]

This is not for visit the type archive , is aims to help build analyzer get correct assets in prod environment

cr resolved

[ilteoood]

@zhoushaw I think that removing the plugin owner from the review is an highly unprofessional behaviour.
How can you approve a PR that:

• has some tests removed even if no code base has been changed;
• has tons of untested code;
• comes without the proper changes to the plugin's README file;
• comes with a rollback of the plugin version.

Lots of comments I made have been ignored, but in the end this has been merged anyway, bringing into the plugin lots of crappy code full of eslint-ignore comments.

I don't know if this is your usual way of work, but please stop ruining the work of people who try to keep high standards.

[zhoushaw]

@ilteoood I apologize for changing the reviewer's behavior, because Zhang Hang told me that the relevant problem has been fixed, and I saw that the relevant comments have been resolved，It seems that lint rules do not restrict some syntax content, is it possible to adjust lint to automatically handle some non-standard code?

[zhoushaw]

@2heal1 It seems that some of our errors have not been fixed, and I think we should fix this part of the optimization as soon as possible

[zhoushaw]

@ilteoood For code style, I think we can add lint to handle

[ScriptedAlchemy]

@ilteoood apologies for this. We will work to rectify this and appreciate your effort, input, and feedback.

I can understand your frustration, but lets maintain a friendly correspondence in feedback.
I believe some things slipped through the cracks here and ultimately lead to a frustrations.

In the future we will be more careful regarding input and overwrites to other authored works.

growing pains

[zhoushaw]

https://github.com/module-federation/universe/blob/main/CODE_OF_CONDUCT.md

We will maintain the above code of conduct, If there are problems and feedback, we will accept the feedback with sincerity and patience and improve it, but we refuse to communicate in an unfriendly way

[zhoushaw]

I will give some feedback on the points mentioned in this pr：

• The test file content has been adjusted and more tests have been added
• Rpc file test file missing can be optimized, and test coverage card points can be added later
• readme has been tweaked and a new version of the documentation has gone live
• The incorrect version will be fixed immediately chore: native typescript remove all eslint annotation and rollback version #2285

The code style issues with the comments should all have been fixed，This part is best constrained and automated through prettierrc and lint rule sets