Unable to build Jupyter lab 3.0.14

Jupyter lab version= 3.0.14 python = 3.8.2 OS= Windows 10pro After installing jupyter labextension spreadsheet jupyter lab failed to build. If i uninstall it then build successfully.

C:\Users\PC>jupyter labextension install jupyterlab-spreadsheet --no-build

C:\Users\PC>jupyter lab build --minimize=False [LabBuildApp] JupyterLab 3.0.14 [LabBuildApp] Building in C:\Program Files\Autosphere\Process Studio\App\Python\share\jupyter\lab [LabBuildApp] Building jupyterlab assets (production, not minimized) Build failed. Troubleshooting: If the build failed due to an out-of-memory error, you may be able to fix it by disabling the dev_build and/or minimize options.

If you are building via the jupyter lab build command, you can disable these options like so:

jupyter lab build --dev-build=False --minimize=False

You can also disable these options for all JupyterLab builds by adding these lines to a Jupyter config file named jupyter_config.py:

c.LabBuildApp.minimize = False c.LabBuildApp.dev_build = False

If you don’t already have a jupyter_config.py file, you can create one by adding a blank file of that name to any of the Jupyter config directories. The config directories can be listed by running:

jupyter --paths

Explanation:

• dev-build: This option controls whether a dev or a more streamlined production build is used. This option will default to False (i.e., the production build) for most users. However, if you have any labextensions installed from local files, this option will instead default to True. Explicitly setting dev-build to False will ensure that the production build is used in all circumstances.

• minimize: This option controls whether your JS bundle is minified during the Webpack build, which helps to improve JupyterLab’s overall performance. However, the minifier plugin used by Webpack is very memory intensive, so turning it off may help the build finish successfully in low-memory environments.

An error occured. RuntimeError: JupyterLab failed to build See the log file for details: C:\Users\PC\AppData\Local\Temp\jupyterlab-debug-9p9orm7d.log

[caexy]

Could you please provide the error log? I tried to reinstall it today and it worked。

[quigleyj97]

Unable to reproduce that exact failure, but after updating dependencies I did encounter one very similar build failure relating to that same hack. The format that expose-loader uses changed from 0.7.5 to 1.x, and now requires an exposes property to signal what the exported symbols are.