From bd54341c6485d86e73ce439da230bee3c802b99d Mon Sep 17 00:00:00 2001 From: Hope Hadfield Date: Tue, 20 Jan 2026 10:22:37 -0500 Subject: [PATCH] implement suggestions Signed-off-by: Hope Hadfield --- packages/backend-dynamic-feature-service/README.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/packages/backend-dynamic-feature-service/README.md b/packages/backend-dynamic-feature-service/README.md index 330845f22d..8122810f96 100644 --- a/packages/backend-dynamic-feature-service/README.md +++ b/packages/backend-dynamic-feature-service/README.md @@ -1,12 +1,12 @@ # @backstage/backend-dynamic-feature-service -This package provides support for **dynamic backend features (plugins and modules)** in Backstage, allowing you to load plugins at runtime from a separate directory without including them in your main application's package.json. +This package provides experimental support for **dynamic backend features (plugins and modules)** in Backstage, allowing you to load plugins at runtime from a separate directory without including them in your main application's package.json. ## Purpose This enables: -- **Plugin distribution**: Distributing plugins as standalone packages +- **Plugin distribution**: Distributing plugins as standalone artifacts - **Runtime flexibility**: Adding or updating plugins without rebuilding the entire application - **Isolation**: Keeping plugin-specific dependencies separate from core application dependencies - **Modular deployments**: Different environments can load different sets of plugins @@ -136,8 +136,6 @@ yarn install # Installs all the plugin's dependencies **Example scenario:** Plugin needs `axios@1.4.0` which isn't available in the main application. -**Limitation:** `@backstage/*` dependencies will also be installed in the plugin's `node_modules` and will take priority over the main application's versions, leading to a big number of unnecessary duplicated dependencies, and potentially breaking consistency between core Backstage packages. - ### 3. Custom packaging CLI tool **When to use:** When you want to produce self-contained dynamic plugin packages that can be directly extracted without any post-action, and systematically use the core `@backstage` dependencies provided by the Backstage application.