Closed mbeckert closed 2 years ago
successfully tested the new core with the following test-scenarios considering old (classic hotloader) and new boilerplate (webpack5 wmf) - in DEV and PROD env.
test-scenario | DEV classic hotloading | PROD classic hotloading | DEV webpack module federation | PROD webpack module federation |
---|---|---|---|---|
nested routing | √ | √ | √ | √ |
swidget has further dependency (unknown to host) | √ | √ | √ | √ |
swidget consumes DI Binding from host | √ | √ | √ | √ |
swidget re-binds DI Binding from host | √ | √ | √ | √ |
interconnection between host and swidget | √ | √ | √ | √ |
@mbeckert rebase please to resolve conflicts
First findings:
Can't perform a React state update on an unmounted component. This is a no-op, but it indicates a memory leak in your application. To fix, cancel all subscriptions and asynchronous tasks in a useEffect cleanup function. in RouterProvider (created by swidget)
WMF
host-app
webpack/base.js
src/routes/Home.tsx
<SwidgetLoader url="http://127.0.0.1:7070/swidgetEntry.js" scope="swidget" module="app" />
swidget-app
webpack/base.js
router
route-declaration
NEW
OLD
service
navigateTo()
linkToHome()
andnavigateToHome()
as deprecated since there is no fix home-routeroute-serializers
Path (default)
QueryString (default as swidget)
Hashbang
Link-Component