From 993c69ea3052f443284c987989ac5b1f354952ba Mon Sep 17 00:00:00 2001 From: Enas Gaber Date: Thu, 11 Jun 2026 14:32:54 +0200 Subject: [PATCH] Update docs for including assets of widgets in the react client bundle --- .../apidocs/studio-pro-10/pluggable-widgets/_index.md | 3 ++- .../apidocs/studio-pro-11/pluggable-widgets/_index.md | 3 ++- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/content/en/docs/apidocs-mxsdk/apidocs/studio-pro-10/pluggable-widgets/_index.md b/content/en/docs/apidocs-mxsdk/apidocs/studio-pro-10/pluggable-widgets/_index.md index 76685538db4..74dcb475679 100755 --- a/content/en/docs/apidocs-mxsdk/apidocs/studio-pro-10/pluggable-widgets/_index.md +++ b/content/en/docs/apidocs-mxsdk/apidocs/studio-pro-10/pluggable-widgets/_index.md @@ -68,7 +68,8 @@ A widget package file is just a ZIP archive containing the following things: * *{widgetName}.tile.png* sets the tile image inside the Studio Pro toolbox in tile view (the ideal image size is 256x192 pixels, but other sizes will be resized to fit) * *{widgetName}.tile.dark.png* sets the dark-mode equivalent to *{widgetName}.tile.png* * Optionally, some widget-related resources, preferably located next to the file which contains the client component - * Note that all CSS files you add (except the one located in the **lib** sub-directory) will automatically be loaded in an app via the widget + * All CSS files you add (except the one located in the **lib** sub-directory) will automatically be loaded in an app via the widget. + * When the React Client is enabled for an app, any `assets` directories in a widget package are automatically copied to the widget's directory under `dist` during bundling. This ensures that all asset files from a pluggable widget are included in the final build and available at runtime. * Optionally, a *locales* folder. Naming your widget package file after the `widgetName` is best practice. Also, a widget package can include multiple widgets by putting several of the above items in the same widget package. However, creating such packages is *not recommended*. diff --git a/content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/pluggable-widgets/_index.md b/content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/pluggable-widgets/_index.md index 1982a432313..e34fa601e29 100644 --- a/content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/pluggable-widgets/_index.md +++ b/content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/pluggable-widgets/_index.md @@ -69,7 +69,8 @@ A widget package file is just a ZIP archive containing the following things: * *{widgetName}.tile.png* sets the tile image inside the Studio Pro toolbox in tile view (the ideal image size is 256x192 pixels, but other sizes will be resized to fit) * *{widgetName}.tile.dark.png* sets the dark-mode equivalent to *{widgetName}.tile.png* * Optionally, some widget-related resources, preferably located next to the file which contains the client component - * Note that all CSS files you add (except the one located in the **lib** sub-directory) will automatically be loaded in an app via the widget + * All CSS files you add (except the one located in the **lib** sub-directory) will automatically be loaded in an app via the widget. + * When the React Client is enabled for an app, any `assets` directories in a widget package are automatically copied to the widget's directory under `dist` during bundling. This ensures that all asset files from a pluggable widget are included in the final build and available at runtime. Naming your widget package file after the `widgetName` is best practice. Also, a widget package can include multiple widgets by putting several of the above items in the same widget package. However, creating such packages is *not recommended*.