@backstage/frontend-dynamic-feature-loader 0.1.10-next.2 → 0.1.11-next.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/CHANGELOG.md +18 -0
  2. package/README.md +5 -4
  3. package/package.json +5 -5
package/CHANGELOG.md CHANGED
@@ -1,5 +1,23 @@
1
1
  # @backstage/frontend-dynamic-feature-loader
2
2
 
3
+ ## 0.1.11-next.0
4
+
5
+ ### Patch Changes
6
+
7
+ - Updated dependencies
8
+ - @backstage/frontend-plugin-api@0.15.2-next.0
9
+ - @backstage/config@1.3.6
10
+ - @backstage/module-federation-common@0.1.2
11
+
12
+ ## 0.1.10
13
+
14
+ ### Patch Changes
15
+
16
+ - e8ba654: Update the README of the `frontend-dynamic-feature-loader` package to mention the new `backstage-cli package bundle` command.
17
+ - Updated dependencies
18
+ - @backstage/frontend-plugin-api@0.15.0
19
+ - @backstage/module-federation-common@0.1.2
20
+
3
21
  ## 0.1.10-next.2
4
22
 
5
23
  ### Patch Changes
package/README.md CHANGED
@@ -22,11 +22,12 @@ The frontend feature loader provided in this package works hand-in-hand with the
22
22
 
23
23
  Adding a frontend plugin (with new frontend system support, possibly in alpha support), is straightforward and consists in:
24
24
 
25
- - building the frontend plugin with the `frontend-dynamic-container` role, which enables the module federation support, and packages the plugin as a module remote
26
- - copying the frontend package folder, with the `dist` folder generated during the build, to the dynamic plugins root folder of the Backstage installation (defined by the `dynamicPlugins.rootDirectory` configuration value, which is usually set as `dynamic-plugins-root`).
25
+ - bundling the frontend plugin with the [`backstage-cli package bundle`](../../docs/tooling/cli/03-commands.md#package-bundle) command, thus producing a self-contained bundle based on Module Federation.
26
+ - copying the bundle folder into the Backstage installation dynamic plugins root folder for dynamic loading.
27
27
 
28
- So from a frontend plugin package folder, you would use the following command:
28
+ So from a `my-backstage-plugin` frontend plugin package folder, you would use the following command:
29
29
 
30
30
  ```bash
31
- yarn build --role frontend-dynamic-container && cp -R $(pwd) <target backstage>/dynamic-plugins-root/
31
+ yarn backstage-cli package bundle --output-destination /path/to/dynamic-plugins-root
32
+ # Creates a self-contained bundle in the /path/to/dynamic-plugins-root/my-backstage-plugin/ sub-folder
32
33
  ```
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@backstage/frontend-dynamic-feature-loader",
3
- "version": "0.1.10-next.2",
3
+ "version": "0.1.11-next.0",
4
4
  "backstage": {
5
5
  "role": "web-library"
6
6
  },
@@ -33,8 +33,8 @@
33
33
  },
34
34
  "dependencies": {
35
35
  "@backstage/config": "1.3.6",
36
- "@backstage/frontend-plugin-api": "0.15.0-next.1",
37
- "@backstage/module-federation-common": "0.1.2-next.0",
36
+ "@backstage/frontend-plugin-api": "0.15.2-next.0",
37
+ "@backstage/module-federation-common": "0.1.2",
38
38
  "@module-federation/enhanced": "^0.21.6",
39
39
  "@module-federation/runtime": "^0.21.6",
40
40
  "@module-federation/sdk": "^0.21.6",
@@ -42,8 +42,8 @@
42
42
  "uri-template": "^2.0.0"
43
43
  },
44
44
  "devDependencies": {
45
- "@backstage/cli": "0.36.0-next.2",
46
- "@backstage/test-utils": "1.7.16-next.0",
45
+ "@backstage/cli": "0.36.1-next.0",
46
+ "@backstage/test-utils": "1.7.17-next.0",
47
47
  "@testing-library/jest-dom": "^6.0.0",
48
48
  "@testing-library/react": "^16.0.0",
49
49
  "@types/react": "^18.0.0",