search

rbuckton / reflect-metadata

Prototype for a Metadata Reflection API for ECMAScript
https://rbuckton.github.io/reflect-metadata
Apache License 2.0
3.21k stars 184 forks source link

Version conflicts occur in micro front-end projects #163

Open loca-spirit opened 6 months ago

loca-spirit commented 6 months ago

Because typescript5 is used, version 0.2.2 is used. However, when used with 0.1.13 in a micro front-end project, Reflect.getMetadata('design:type', x, x) will fail.

Scenes: The micro front-end framework is used to load multiple pages. The current page uses (0.1.13), then enters other pages (uses 0.2.2), and then returns to the old page, click to partially load the module through the tab component. There must be a problem that Reflect.getMetadata('design:type',x,x) fails.

But because the scene is too complicated and I don’t understand the underlying storage principle of metadata, I came here to ask for advice.

expect It is expected that versions 0.1.13 and 0.2.2 will be compatible with each other.

rbuckton commented 6 months ago

0.2.2 should be compatible with 0.1.13 as 0.2.2 has a fallback mechanism that captures the various metadata functions from previous versions before replacing them. If you could put together a minimal repro I can investigate.

In the meantime, if you are using a package manager like npm, yarn, or pnpm you can work around the version conflict using any of those package managers' override mechanisms: