paulononato/backstage
1
0
Fork 0
Code Issues Pull Requests Actions 37 Packages Projects Releases Wiki Activity

implement suggestions

Browse Source 
Signed-off-by: Hope Hadfield <hhadfiel@redhat.com>
This commit is contained in:
Hope Hadfield
2026-01-20 10:22:37 -05:00
parent 9b4c4145d4
commit bd54341c64
1 changed files with 2 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
packages/backend-dynamic-feature-service/README.md
+2 -4
View File
@@ -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.