Hina Khadim

@regisb Can you please provide insights on it? If there is no more discussion on it, we can close this.

Just went through the above discussion, why are not we simply include plugin packages in `post-npm-install` and add those plugins in `env.config.jsx`. Then, copy `env.config.jsx` file from the `tutor-mfe` to...

Thanks for asking. I have made all improvements and no further action is reqiured.

My final insights after running everything: **_First-time build or --no-cache build:_** - All enabled MFEs try to install from npm. No npm cache is used. (Due to parallelism) **_Second time...

Updates: With `--no-cache` flag: I tried building MFE image with the `--no-cache` on the sandbox server. There I got a cache hit which shows that the npm cache is being...

@tasawar-hussain suggested three ways to consider the cache usage for MFE build: 1. [multi stage builds](https://codefresh.io/docker-tutorial/node_docker_multistage/) This point says to use the multi-stage build feature of Docker that is already...

@DawoudSheraz @regisb I have tested this and working fine. Can you plz review it?

Moved the respective troubleshooting guides to their respective tutor plugins. Will include the links of those sections here. - https://github.com/overhangio/tutor-mfe/pull/200 - https://github.com/overhangio/tutor-indigo/pull/78

The troubleshooting guides have been moved to their respective plugins and the PRs have been merged successfully. It's time to close this PR. Thank you all for your dedicated efforts...

I conclude to two solutions: ### Solution 1: While mounting, add this line in the volume: `/openedx/app/node_modules`. This line will make node_modules a volume (It won't call binding). [Link to...