aurelia / aurelia/webpack-plugin
Webpack + moduleFedrationPlugin + translations of shared components not working
- Dominant language
- TypeScript
- Stars
- 89
- Forks
- 33
- PR merge metrics
- No merged PRs in 30d
Description
**I'm submitting a bug report**
* **Library Version:**
major.minor.patch-pre
5.72.0
**Please tell us about your environment:**
* **Operating System:**
macOs Ventura 13.1
* **Node Version:**
6.2.0
14.19.3
* **NPM Version:**
6.14.7
* **JSPM OR Webpack AND Version**
webpack 5.72.0
* **Browser:**
all
* **Language:**
TypeScript X4.6.3
**Current behavior:**
When used ModuleFedrationPlugin container to share the component from App1 to App2, translations are not been translated and only Keys are visible in App2 UI
App1 webpack looks like :
App2 webpack looks like:
Components in App2 (from App1) looks like

**Expected/desired behavior:**
In App2, the shared components should come up with translations and not only key
* **What is the expected behavior?**
The shared components should come up with translations and not only key
* **What is the motivation / use case for changing the behavior?**
translationd not coming up
I even tried adding react-i18next to peerDependencies but it didn't worked
Contributor guide
Research direction
Start by reproducing the issue with the App1 and App2 webpack configurations shown in the report, then inspect how the shared components initialize translations across the ModuleFederationPlugin boundary. Done means the components rendered in App2 display translated text rather than translation keys.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, webpack
- Domain
- build-system, frontend, internationalization
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100