Skip to content

Commit 0c82cc5

Browse files
authored
Merge pull request #11358 from mendix/ctl-SP11-asset-directories-widgets
Assets directories of widgets in the app bundle (SP11 PR)
2 parents d7adb39 + 1f8d215 commit 0c82cc5

1 file changed

Lines changed: 2 additions & 1 deletion

File tree

  • content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/pluggable-widgets

content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/pluggable-widgets/_index.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,8 @@ A widget package file is just a ZIP archive containing the following things:
6969
* *{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)
7070
* *{widgetName}.tile.dark.png* sets the dark-mode equivalent to *{widgetName}.tile.png*
7171
* Optionally, some widget-related resources, preferably located next to the file which contains the client component
72-
* 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
72+
* All CSS files you add (except the ones located in the **lib** sub-directory) will automatically be loaded in an app via the widget.
73+
* 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.
7374

7475
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*.
7576

0 commit comments

Comments
 (0)