Describe the Bug

Problems when rendering stuff (htmls... svgs...) when having both Client plugin and Pallete (or any other) Provider plugin.

Steps to Reproduce

https://github.com/billbarni/camunda-modeler-plugin-react-test

1 - add project dir to your modeler resources/plugin dir
2 - npm i in project dir
3 - npm run dev in project dir
4 - open modeler and create new Cam 7 BPM

You can see that the Pallete of Camunda Modeler is not able to render the icon correctly.

client/pallete/user-palette-provider.js - lines 22 to 37.

Expected Behavior

IconContext.Provider from react-icons to work... or to ReactDOMServer.renderToString to work...
Or some other way of converting the React icon to HTML inside the modeler plugin

I tried using preact-render-to-string, but it works only with some other bizarre Webpack config, and when it works... the "client" plugin stops working.

Environment

• OS: Windows 10
• Camunda Modeler Version: 5.9.0

People often are not aware of the fact that the name of the bpmn-js module matters (e.g. modules with same name will override others). If they create two plugins without renaming the module they'll wonder why only one of them works.

module.exports = {
  __init__: [ 'clientPlugin' ],
  clientPlugin: [ 'type', ClientPlugin ] // must be renamed
};

We have written several plugins for 3.x, but are looking to upgrade our base modeler that we ship the plugins with. The 4.x upgrade bumped the version of electron significantly and seems to have changed the requirements for plugin development.

Would it be possible to upgrade this plugin example to work with 4.x?