With the Palm release there are some changes in the process of mounting the MFEs for being able to see live changes, and my previous tutorial doesn’t cover it (it covers up to Olive release) so, when I have some time, I will update this part or anything else might come to my attention that works differently.
Hello again @arbrandes !
It’s been a while, but only lately I managed to find the time to check this ( mfe-dockerfile-post-npm-install-learning), but I didn’t manage to make it work as well due to errors while building the mfe image after creating the plugin that makes my MFEs to use my custom frontend-app-footer (and header)…
My plugin looks like this:
from tutor import hooks
hooks.Filters.ENV_PATCHES.add_items(
[
(
"mfe-dockerfile-post-npm-install-learning",
"""
RUN npm install '@edx/frontend-component-footer@git+https://github.com/dagg/frontend-component-footer.git#dagg_palm2_master'
"""
),
(
"mfe-dockerfile-post-npm-install-account",
"""
RUN npm install '@edx/frontend-component-footer@git+https://github.com/dagg/frontend-component-footer.git#dagg_palm2_master'
"""
),
]
)
In this particular one I make the frontend-app-learning and frontend-app-account to use the frontend-component-footer from my dagg_palm2_master branch which I derived from the master branch of the forked frontend-component-footer.
I have tried also with another branch I created from the V12.0.0 Tag (among others) but still I got the same errors while running tutor images build mfe …
I am not sure what’s wrong with it exactly but it doesn’t seem to me like a dependency problem rather than a problem with the building process that doesn’t find certain things.
I might be mistaken though since my knowledge with npm and whatever is involved in building a project with dependencies is quite limited.
I have the whole error trace in the following github gist:
https://gist.github.com/dagg/bba31898169a1a36e6088b770637ac10
I hope it’s something trivial that can be easily corrected!
Any suggestions?