When doing a develop install, R3F visualisations freeze the browser

[loichuder]

Describe the bug

When the extension was installed in "dev mode", it is not possible to display a R3F visualisation: it freezes the browser.

Displaying scalar values, navigating in the file or inspecting entities do not trigger this freeze.

To Reproduce

1. Install the extension according to https://github.com/silx-kit/jupyterlab-h5web/blob/main/CONTRIBUTING.md#install
2. Run jupyter lab
3. Open a HDF file with nD datasets inside
4. Open a nD dataset
5. The browser will freeze

Interestingly, this does not happen with a regular installation pip install .

Context

• Browser: any
• Version: 1.0.0
• JupyterLab version: 3

Reported in #48

[loichuder]

When stopping the script with Firefox, react-reconciler.development.js:15120 gives the following message:

Script terminated by timeout at:
handleError@http://localhost:8890/lab/extensions/jupyterlab-h5web/static/vendors-node_modules_h5web_app_dist_index_js.645b31f0d2716e7e0dd3.js:77424:25
renderRootSync@http://localhost:8890/lab/extensions/jupyterlab-h5web/static/vendors-node_modules_h5web_app_dist_index_js.645b31f0d2716e7e0dd3.js:77538:18
performSyncWorkOnRoot@http://localhost:8890/lab/extensions/jupyterlab-h5web/static/vendors-node_modules_h5web_app_dist_index_js.645b31f0d2716e7e0dd3.js:77125:18
workLoop@http://localhost:8890/lab/extensions/jupyterlab-h5web/static/vendors-node_modules_h5web_app_dist_index_js.645b31f0d2716e7e0dd3.js:88424:42
flushWork@http://localhost:8890/lab/extensions/jupyterlab-h5web/static/vendors-node_modules_h5web_app_dist_index_js.645b31f0d2716e7e0dd3.js:88397:14
performWorkUntilDeadline@http://localhost:8890/lab/extensions/jupyterlab-h5web/static/vendors-node_modules_h5web_app_dist_index_js.645b31f0d2716e7e0dd3.js:88164:48
EventHandlerNonNull*./node_modules/scheduler/cjs/scheduler.development.js/<@http://localhost:8890/lab/extensions/jupyterlab-h5web/static/vendors-node_modules_h5web_app_dist_index_js.645b31f0d2716e7e0dd3.js:88187:3

[loichuder]

The handleError is triggered by a variable ReactDebugCurrentFrame$1 that is undefined.

We seem to be in the following case: facebook/react#14137 (comment)

[loichuder]

Ok so by running jlpm build:prod locally instead of jlpm build, I can have the vis working. I will document this and we can close the issue.