# Replacing Modulus: Project Status Updates

**URL:** <https://talk.openmrs.org/t/replacing-modulus-project-status-updates/9789>\
**Category:** Modulus\
**Tags:** pm-status-update\
**Created:** [January 27, 2017, 5:30pm UTC](https://talk.openmrs.org/t/replacing-modulus-project-status-updates/9789 "2017-01-27T17:30:53Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![reubenv](https://talk.openmrs.org/user_avatar/talk.openmrs.org/reubenv/32/3818_2.png) [@reubenv](https://talk.openmrs.org/u/reubenv)\
**Post date:** [March 15, 2017, 1:48pm UTC](https://talk.openmrs.org/t/replacing-modulus-project-status-updates/9789/13 "2017-03-15T13:48:24Z")

</div>

Replying to [Add-On Index enhancements - #7 by cintiadr](https://talk.openmrs.org/t/add-on-index-enhancements/10531/7) here, because the other thread was made with the intention of gsoc discussions on the project.

> [@Add-On Index enhancements](https://talk.openmrs.org/t/add-on-index-enhancements/10531/7):
>
> No luck.
> 
> I tried to run it locally, I went to [https://github.com/openmrs/openmrs-contrib-ansible-docker-compose/tree/master/files/addons-stg](https://github.com/openmrs/openmrs-contrib-ansible-docker-compose/tree/master/files/addons-stg) , docker-compose pull && docker-compose up , using on the browser [http://localhost:8081](http://localhost:8081), exactly same behaviour.
> 
> And if you look the source code of the page, your change is there.

It’s funny how the smallest of issues sometimes get us(me in this case) stuck 😅. The reason for the console error was basically that although the new url pointed to “react-router”, it pointed to “react-router v4.0” whereas our project previously depended on “ReactRouter” which was part of V3.0.2 .

**The next question is as to how did this happen in the first place?**

The answer to this is that we previously used a url which was dynamic i.e. it gets resolved to a different one .The url used was [this](https://unpkg.com/react-router/umd/ReactRouter.min.js). This url basically points to the latest version of react router which is now V4.0 . Now, if we look into the contents of [this resolved url](https://unpkg.com/react-router@4.0.0/umd/) , we realise that ReactRouter.min.js no longer exists and that only react-router.js is present. Hence , naturally I didn’t initially think that there’s going to be a difference between the two and created a pull request with a url pointing to react-router.js .

> [@Add-On Index enhancements](https://talk.openmrs.org/t/add-on-index-enhancements/10531/8):
>
> The build ([https://app.snap-ci.com/openmrs/openmrs-contrib-addonindex/branch/master](https://app.snap-ci.com/openmrs/openmrs-contrib-addonindex/branch/master)) looks ok, it appears to have updated the docker image ([Docker](https://hub.docker.com/r/openmrs/addonindex/tags/)), I confirmed the docker image running is the latest image.
> 
> On Chrome console, I have for both the deployed site and running locally:

This new file missed some vital code on which our project currently depends and hence the console error . On checking the npm package.json file, I realised that we were using v3.0.2 and when I navigated to the [React-router files of v3.0.2](https://unpkg.com/react-router@3.0.2/umd/), I found the file right there. Hence I have now created an updated PR with the link to the exact same file. I have also tested it locally and can confirm that Add-On Index is back up and running 🙂 .

@darius Please check [this](https://github.com/openmrs/openmrs-contrib-addonindex/pull/6) .🙂

---

_[View the full topic](https://talk.openmrs.org/t/replacing-modulus-project-status-updates/9789)._