![]() For example, if you added your own MFE named frontend-app-myapp, then you can bind-mount it like so: The changes you make to your fork will be automatically picked up and hot-reloaded by your development server. Npm install # Ensure NPM requirements are installed into your fork. You can also bind-mount your own fork of an MFE. Tutor makes it possible to run any MFE in development mode. RUN npm install same applies to installing a custom brand package: ![]() To install custom components for the MFEs, such as the header and footer, override the components by adding a patch to mfe-dockerfile-post-npm-install in your plugin: If patches are the same in development and production, they can be replaced by a single mfe-lms-common-settings patch. To change the MFEs logos from the default to your own logos, override the corresponding settings in the MFEs environment using patches mfe-lms-production-settings and mfe-lms-development-settings. Your custom translation strings should now appear in your app. Rebuild the MFE image and restart the MFE with: For instance, to add French ("fr") translation strings to the account MFE, run:Ĭd "$(tutor config printroot)/env/plugins/mfe/build/mfe/i18n/"Īdd your entries to this file in JSON format, where the key is the string ID and the value is the actual string. This location of this file should be /path/to/tutor/env/plugins/mfe/build/mfe/i18n//.json. ![]() For instance, the ID of the "Account Information" string in the account MFE is ".information" (see source).Ĭreate a folder and i18n file corresponding to your MFE app and language in the Tutor root. Identify the ID of the string you would like to translate. This plugin makes it possible to change existing and add new translation strings to MFEs.
0 Comments
Leave a Reply. |