Look into removing material ui packages

[kevin-bates]

Users running in hosted environments with slower network latencies are experiencing Elyra startup delays that may be due to the lack of material ui packaging optimization. We should understand where these costs are occurring and only packaging what is absolutely necessary for the proper functioning of Elyra.

[ajbozarth]

We currently still use Material UI in three places:

1. Toast notifications in pipeline-editor
2. Theme Provider in ui-components
3. The Metadata Header UI in metadata-common

As for removing these:

1. Toast notifications are being added to core in 4.0, we can either wait or directly use the library they are merging into core (I believe it's not new code)
2. We already wanted to remove StyleProvider, so we can see how much we leverage ThemeProvider vs just generically wrap it ourselves
3. This will be the hardest since all the header functionality uses material ui and we will need to rewrite it

[jschaeck]

Not sure if this helps at all but material ui have some proposals how to minimize component size, maybe this could help to improve the situation till it is completely removed?

https://mui.com/material-ui/guides/minimizing-bundle-size/

[ptitzler]

We currently still use Material UI in three places:

1. Toast notifications in pipeline-editor
2. Theme Provider in ui-components
3. The Metadata Header UI in metadata-common

We've discussed this in today's dev meeting:

• Item 1 does not contribute to the reported performance issue. Thus there is no urgent need to address this right away and work can be held until JupyterLab 4.0 becomes available.
• Work for item 2 will be tracked in Migrate off material UI in the Theme Provider #2951
• Work for item 3 will be tracked in Migrate off material UI in the Metadata Header UI #2952

[ptitzler]

@jschaeck please subscribe to those issues