Using packaged openimis-fe-core module in development mode leads to React Router instantiation problem

Description

When developing a new frontend module, one should used the latest packaged version of openimis-fe-core.
However, doing this leads to Router error (see here under).

Workaround is to use openimis-fe-core locally (with yarn link)
... BUT this is making things more complex than it should...

tiny-invariant.esm.js:13 Uncaught Error: Invariant failed: You should not use <withRouter(Contributions) /> outside a <Router>
at invariant (tiny-invariant.esm.js:13)
at react-router.js:674
at updateContextConsumer (react-dom.development.js:18201)
at beginWork (react-dom.development.js:18551)
at HTMLUnknownElement.callCallback (react-dom.development.js:189)
at Object.invokeGuardedCallbackDev (react-dom.development.js:238)
at invokeGuardedCallback (react-dom.development.js:291)
at beginWork$1 (react-dom.development.js:23052)
at performUnitOfWork (react-dom.development.js:22016)
at workLoopSync (react-dom.development.js:21992)
at performSyncWorkOnRoot (react-dom.development.js:21610)
at react-dom.development.js:11130
at unstable_runWithPriority (scheduler.development.js:656)
at runWithPriority$1 (react-dom.development.js:11076)
at flushSyncCallbackQueueImpl (react-dom.development.js:11125)
at flushSyncCallbackQueue (react-dom.development.js:11113)
at discreteUpdates$1 (react-dom.development.js:21749)
at discreteUpdates (react-dom.development.js:811)
at dispatchDiscreteEvent (react-dom.development.js:4210)

Environment

None
Done

Assignee

Purushottam Sapkota

Reporter

Purushottam Sapkota

Labels

None

Priority

Medium
Configure