Releases: dkhrunov/ngx-mfe
Releases · dkhrunov/ngx-mfe
v17.0.0
v16.0.0
v15.1.0
Features:
- Added ability to load MfeConfig asynchronously. [Issue - #18]
Fixed:
- Fixed type of
NGX_MFE_OPTIONS
formInjectionToken<string>
toInjectionToken<NgxMfeOptions>
.
Breaking changes:
- Renamed MfeModule.forRoot() options from
NgxMfeOptions
toNgxMfeForRootOptions
. - Now
MfeRegistry
is no longer accessible from DI. - Changed API of
MfeRegistry
:- changed method
public static getInstance(mfeConfig?: MfeConfig): MfeRegistry
to getterpublic static get instance(): MfeRegistry
; - added method
public setMfeConfig(config: MfeConfig): void
.
- changed method
v15.0.0
v3.0.2
v3.0.1
v3.0.0
v2.1.0
Fixed:
- Fix error, if the fallback is also unavailable, then simply clear the view;
Refactored:
- Renamed
MfeService
toRemoteComponentLoader
; - Renamed
MfeComponentsCache
toRemoteComponentsCache
; - Renamed
ModularRemoteComponent
type toRemoteComponentWithModule
; - Wrapped to
ngZone.runOutside
theloadMfe
function calls inside theRemoteComponentLoader
; - Added new type
ComponentWithNgModuleRef<TComponent, TModule>
, that holds component classType<T>
andNgModuleRef
; - Changed cached value for
RemoteComponentWithModule
fromComponentFactory
toComponentWithNgModuleRef
; - In
RemoteComponentLoader
(old nameMfeService
) renamed functionloadModularComponent
toloadComponentWithModule
- Changed return type of method
loadComponentWithModule
inside classRemoteComponentLoader
fromPromise<ComponentFactory<TComponent>>
toPromise<ComponentWithNgModuleRef<TComponent, TModule>>
;
v2.0.0
Why has the API changed? - The problem is that when you use the [mfeOutlet]
directive issue, it tries to find the component inside the compiled module by name (as a string), but in runtime the class name will be optimized and replaced with a short character. For example, you have a class TestComponent
, it can be changed to the class name a
and this causes this error.