With time we added more details and more levels to the locations for every country, and this is making the library quite big. This is a problem for front end applications. One solution found by @jofomah was to keep the list of locations in a database, and download them when the application starts. Another possibility is to simply split the library, so that an application running for users in Sierra Leone will not need to carry all details about locations in Liberia. This is what this issue is about, splitting the library. This has to be done together with an user application (something like the Sense dashboard, the Call Centre or the Sense followup), in order to be sure that the way the split version is distributed is suitable to be used conveniently by the apps

Apparently the issue is on this line

Particularly for dependency resolving

This is done often in map functions and other code close to user interaction, where is preferable to not break the control flow. In our specific case a modal was never showing up and a spinner was running on the page forever