You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/dynamic-plugins/proc-create-plugin-js-package.adoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,6 +34,6 @@ You can add the following to your `package.json` file before running the `export
34
34
}
35
35
----
36
36
37
-
If you modify `publishConfig` after exporting the dynamic plugin, re-run the `export-dynamic-plugin` command to ensure the correct configuration is included.
37
+
If you modify `publishConfig` after exporting the dynamic plugin, re-run the `plugin export` command to ensure the correct configuration is included.
Copy file name to clipboardExpand all lines: modules/dynamic-plugins/proc-export-third-party-plugins-rhdh.adoc
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@
4
4
To use plugins in {product}, you can export plugins as derived dynamic plugin packages. These packages contain the plugin code and dependencies, ready for dynamic plugin integration into {product-short}.
5
5
6
6
.Prerequisites
7
-
* The `@janus-idp/cli` package is installed. Use the latest version (`@latest` tag) for compatibility with the most recent features and fixes.
7
+
* The `@red-hat-developer-hub/cli` package is installed. Use the latest version (`@latest` tag) for compatibility with the most recent features and fixes.
8
8
* Node.js and NPM is installed and configured.
9
9
* The third-party plugin is compatible with your {product} version. For more information, see link:https://github.com/redhat-developer/rhdh/blob/main/docs/dynamic-plugins/versions.md[Version compatibility matrix].
10
10
* The third-party plugin must have a valid `package.json` file in its root directory, containing all required metadata and dependencies.
@@ -35,7 +35,7 @@ The following is an example of exporting a dynamic plugin with shared and embedd
35
35
.Example dynamic plugin export with shared and embedded packages
Copy file name to clipboardExpand all lines: modules/proc-create-plugin.adoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,7 +32,7 @@ The previous command creates a new plugin based on the provided ID. The plugin i
32
32
yarn workspace {pluginID} start # Also supports --check <1>
33
33
----
34
34
35
-
<1> ID of the new plugin such as `@janus-idp/my-new-plugin`
35
+
<1> ID of the new plugin such as `@red-hat-developer-hub/my-new-plugin`
36
36
37
37
Accessing the plugin in isolation results in quicker iteration and startup times. This approach is specifically for local development, and you can find the necessary configuration in the plugin's `dev/` directory.
The `@latest` tag pulls the latest version of the @janus-idp/cli package, which is compatible with the most recent features and fixes. Use a version that is compatible with your {product} version.
34
+
The `@latest` tag pulls the latest version of the @red-hat-developer-hub/cli package, which is compatible with the most recent features and fixes. Use a version that is compatible with your {product} version.
35
35
====
36
36
. To package the third-party TechDocs add-on as a dynamic plugin, navigate to the root directory where the plugin is stored (not the dist-dynamic directory) and run the `npx` command with the `--tag` option to specify the image name and tag. For example:
0 commit comments