From 858eb692075e6de2bd983a158df86da88c3d0b66 Mon Sep 17 00:00:00 2001 From: Hyun Don Moon Date: Sat, 26 Apr 2025 00:02:41 +0900 Subject: [PATCH] docs(misc): fix typo in microfrontend architecture article (#29911) ## Current Behavior There's a typo in the [microfrontend architecture article](https://nx.dev/concepts/module-federation/micro-frontend-architecture#shared-libraries) under the "Shared Libraries" section. `The default the Nx setup configures` ## Expected Behavior Should be `The default Nx setup configures` Fixes # --- .../concepts/module-federation/micro-frontend-architecture.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/shared/concepts/module-federation/micro-frontend-architecture.md b/docs/shared/concepts/module-federation/micro-frontend-architecture.md index f0801a6d78..78ea3a46a3 100644 --- a/docs/shared/concepts/module-federation/micro-frontend-architecture.md +++ b/docs/shared/concepts/module-federation/micro-frontend-architecture.md @@ -97,7 +97,7 @@ in case of a bad deployment. ## Shared libraries Since deployments with MFEs are not atomic, there is a chance that shared libraries -- both external (npm) and workspace -- -between the host and remotes are mismatched. The default the Nx setup configures all libraries as singletons, which requires +between the host and remotes are mismatched. The default Nx setup configures all libraries as singletons, which requires that all affected applications be deployed for any given changeset, and makes à la carte deployments riskier. There are mitigation strategies that can minimize mismatch errors. One such strategy is to share as little as possible