JupyterLab failed to build

Hi everyone, I'm trying to install jupyterlab-prodigy and I've been following the instructions/googling errors with no help. I first did pip install jupyterlab>=2.0.0 as per the docs, and got v3 installed automatically. After that when I ran jupyter labextension install jupyterlab-prodigy, I kept getting the error JupyterLab failed to build.

Here is my error log:

[LabBuildApp] Building in C:\Users\t724614\Anaconda3\share\jupyter\lab
[LabBuildApp] Node v14.17.2

[LabBuildApp] Yarn configuration loaded.
[LabBuildApp] Building jupyterlab assets (production, minimized)
[LabBuildApp] > node C:\Users\t724614\Anaconda3\lib\site-packages\jupyterlab\staging\yarn.js install --non-interactive
[LabBuildApp] yarn install v1.21.1
[1/5] Validating package.json...
[2/5] Resolving packages...
success Already up-to-date.
Done in 0.73s.

[LabBuildApp] > node C:\Users\t724614\Anaconda3\lib\site-packages\jupyterlab\staging\yarn.js yarn-deduplicate -s fewer --fail
[LabBuildApp] yarn run v1.21.1
$ C:\Users\t724614\Anaconda3\share\jupyter\lab\staging\node_modules.bin\yarn-deduplicate -s fewer --fail
Done in 0.70s.

[LabBuildApp] > node C:\Users\t724614\Anaconda3\lib\site-packages\jupyterlab\staging\yarn.js run build:prod:minimize
[LabBuildApp] yarn run v1.21.1
$ webpack --config webpack.prod.minimize.config.js
assets by status 10.1 MiB e[1me[32m[cached]e[39me[22m 116 assets
orphan modules 4.72 MiB e[1me[33m[orphan]e[39me[22m 1253 modules
runtime modules 104 KiB 14 modules
built modules 13.4 MiB (javascript) 4.47 KiB (consume-shared) 4.43 KiB (share-init) e[1me[33m[built]e[39me[22m
modules by path e[1m./node_modules/e[39me[22m 13.3 MiB
cacheable modules 13.3 MiB 975 modules
3 modules
consume-shared-module modules 4.47 KiB
modules by path e[1mconsume shared module (default) @jupyterlab/e[39me[22m 3.53 KiB 41 modules
modules by path e[1mconsume shared module (default) @lumino/e[39me[22m 588 bytes 14 modules
provide-module modules 4.43 KiB 108 modules
modules by path e[1m./build/e[39me[22m 23.3 KiB
e[1m./build/bootstrap.jse[39me[22m 3.78 KiB e[1me[33m[built]e[39me[22m e[1me[33m[code generated]e[39me[22m
e[1m./build/index.out.js + 1 modulese[39me[22m 19.5 KiB e[1me[33m[built]e[39me[22m e[1me[33m[code generated]e[39me[22m
4 modules

e[1me[33mWARNINGe[39me[22m in e[1m./node_modules/vega-lite/build/src/index.jse[39me[22m e[1me[32m5:0-30e[39me[22m
e[1mShould not import the named export 'version' (reexported as 'version') from default-exporting module (only default export is available soon)e[39me[22m
@ consume shared module (default) vega-lite@^4.0.2 (strict) (fallback: ./node_modules/vega-lite/build/src/index.js)
@ ./node_modules/vega-embed/build/vega-embed.module.js 6:0-44 189:15-29
@ consume shared module (default) vega-embed@^6.2.1 (strict) (fallback: ./node_modules/vega-embed/build/vega-embed.module.js)
@ ./node_modules/@jupyterlab/vega5-extension/lib/index.js 166:28-48
@ consume shared module (default) @jupyterlab/vega5-extension@~3.0.7 (strict) (fallback: ./node_modules/@jupyterlab/vega5-extension/lib/index.js)
@ ./build/index.out.js 171:16-54
@ ./build/bootstrap.js

e[1me[31mERRORe[39me[22m in e[1me[32mresolving fallback for shared module jupyterlab-prodigye[39me[22m
e[1mModule e[1me[31mnot founde[39me[22me[1m: e[1me[31mErrore[39me[22me[1m: Can't resolve 'jupyterlab-prodigy' in 'C:\Users\t724614\Anaconda3\share\jupyter\lab\staging\build'e[39me[22m
resolve 'jupyterlab-prodigy' in 'C:\Users\t724614\Anaconda3\share\jupyter\lab\staging\build'
Parsed request is a module
using description file: C:\Users\t724614\Anaconda3\share\jupyter\lab\staging\build\package.json (relative path: .)
Field 'browser' doesn't contain a valid alias configuration
resolve as module
e[1me[31mC:\Users\t724614\Anaconda3\share\jupyter\lab\staging\build\node_modules doesn't existe[39me[22m or is not a directory
looking for modules in C:\Users\t724614\Anaconda3\share\jupyter\lab\staging\node_modules
single file module
using description file: C:\Users\t724614\Anaconda3\share\jupyter\lab\staging\package.json (relative path: ./node_modules/jupyterlab-prodigy)
no extension
Field 'browser' doesn't contain a valid alias configuration
C:\Users\t724614\Anaconda3\share\jupyter\lab\staging\node_modules\jupyterlab-prodigy is not a file
.js
Field 'browser' doesn't contain a valid alias configuration
e[1me[31mC:\Users\t724614\Anaconda3\share\jupyter\lab\staging\node_modules\jupyterlab-prodigy.js doesn't existe[39me[22m
.json
Field 'browser' doesn't contain a valid alias configuration
e[1me[31mC:\Users\t724614\Anaconda3\share\jupyter\lab\staging\node_modules\jupyterlab-prodigy.json doesn't existe[39me[22m
.wasm
Field 'browser' doesn't contain a valid alias configuration
e[1me[31mC:\Users\t724614\Anaconda3\share\jupyter\lab\staging\node_modules\jupyterlab-prodigy.wasm doesn't existe[39me[22m
existing directory C:\Users\t724614\Anaconda3\share\jupyter\lab\staging\node_modules\jupyterlab-prodigy
using description file: C:\Users\t724614\Anaconda3\share\jupyter\lab\staging\node_modules\jupyterlab-prodigy\package.json (relative path: .)
using description file: C:\Users\t724614\Anaconda3\share\jupyter\lab\staging\package.json (relative path: ./node_modules/jupyterlab-prodigy)
no extension
Field 'browser' doesn't contain a valid alias configuration
C:\Users\t724614\Anaconda3\share\jupyter\lab\staging\node_modules\jupyterlab-prodigy is not a file
.js
Field 'browser' doesn't contain a valid alias configuration
e[1me[31mC:\Users\t724614\Anaconda3\share\jupyter\lab\staging\node_modules\jupyterlab-prodigy.js doesn't existe[39me[22m
.json
Field 'browser' doesn't contain a valid alias configuration
e[1me[31mC:\Users\t724614\Anaconda3\share\jupyter\lab\staging\node_modules\jupyterlab-prodigy.json doesn't existe[39me[22m
.wasm
Field 'browser' doesn't contain a valid alias configuration
e[1me[31mC:\Users\t724614\Anaconda3\share\jupyter\lab\staging\node_modules\jupyterlab-prodigy.wasm doesn't existe[39me[22m
as directory
existing directory C:\Users\t724614\Anaconda3\share\jupyter\lab\staging\node_modules\jupyterlab-prodigy
using description file: C:\Users\t724614\Anaconda3\share\jupyter\lab\staging\node_modules\jupyterlab-prodigy\package.json (relative path: .)
use ./lib/index.js from main in package.json
using description file: C:\Users\t724614\Anaconda3\share\jupyter\lab\staging\node_modules\jupyterlab-prodigy\package.json (relative path: ./lib/index.js)
no extension
Field 'browser' doesn't contain a valid alias configuration
e[1me[31mC:\Users\t724614\Anaconda3\share\jupyter\lab\staging\node_modules\jupyterlab-prodigy\lib\index.js doesn't existe[39me[22m
.js
Field 'browser' doesn't contain a valid alias configuration
e[1me[31mC:\Users\t724614\Anaconda3\share\jupyter\lab\staging\node_modules\jupyterlab-prodigy\lib\index.js.js doesn't existe[39me[22m
.json
Field 'browser' doesn't contain a valid alias configuration
e[1me[31mC:\Users\t724614\Anaconda3\share\jupyter\lab\staging\node_modules\jupyterlab-prodigy\lib\index.js.json doesn't existe[39me[22m
.wasm
Field 'browser' doesn't contain a valid alias configuration
e[1me[31mC:\Users\t724614\Anaconda3\share\jupyter\lab\staging\node_modules\jupyterlab-prodigy\lib\index.js.wasm doesn't existe[39me[22m
as directory
e[1me[31mC:\Users\t724614\Anaconda3\share\jupyter\lab\staging\node_modules\jupyterlab-prodigy\lib\index.js doesn't existe[39me[22m
using path: C:\Users\t724614\Anaconda3\share\jupyter\lab\staging\node_modules\jupyterlab-prodigy\index
using description file: C:\Users\t724614\Anaconda3\share\jupyter\lab\staging\node_modules\jupyterlab-prodigy\package.json (relative path: ./index)
no extension
Field 'browser' doesn't contain a valid alias configuration
e[1me[31mC:\Users\t724614\Anaconda3\share\jupyter\lab\staging\node_modules\jupyterlab-prodigy\index doesn't existe[39me[22m
.js
Field 'browser' doesn't contain a valid alias configuration
e[1me[31mC:\Users\t724614\Anaconda3\share\jupyter\lab\staging\node_modules\jupyterlab-prodigy\index.js doesn't existe[39me[22m
.json
Field 'browser' doesn't contain a valid alias configuration
e[1me[31mC:\Users\t724614\Anaconda3\share\jupyter\lab\staging\node_modules\jupyterlab-prodigy\index.json doesn't existe[39me[22m
.wasm
Field 'browser' doesn't contain a valid alias configuration
e[1me[31mC:\Users\t724614\Anaconda3\share\jupyter\lab\staging\node_modules\jupyterlab-prodigy\index.wasm doesn't existe[39me[22m
e[1me[31mC:\Users\t724614\Anaconda3\share\jupyter\lab\node_modules doesn't existe[39me[22m or is not a directory
e[1me[31mC:\Users\t724614\Anaconda3\share\jupyter\node_modules doesn't existe[39me[22m or is not a directory
e[1me[31mC:\Users\t724614\Anaconda3\share\node_modules doesn't existe[39me[22m or is not a directory
e[1me[31mC:\Users\t724614\Anaconda3\node_modules doesn't existe[39me[22m or is not a directory
e[1me[31mC:\Users\t724614\node_modules doesn't existe[39me[22m or is not a directory
e[1me[31mC:\Users\node_modules doesn't existe[39me[22m or is not a directory
looking for modules in C:\node_modules
single file module
No description file found in C:\node_modules or above
no extension
Field 'browser' doesn't contain a valid alias configuration
e[1me[31mC:\node_modules\jupyterlab-prodigy doesn't existe[39me[22m
.js
Field 'browser' doesn't contain a valid alias configuration
e[1me[31mC:\node_modules\jupyterlab-prodigy.js doesn't existe[39me[22m
.json
Field 'browser' doesn't contain a valid alias configuration
e[1me[31mC:\node_modules\jupyterlab-prodigy.json doesn't existe[39me[22m
.wasm
Field 'browser' doesn't contain a valid alias configuration
e[1me[31mC:\node_modules\jupyterlab-prodigy.wasm doesn't existe[39me[22m
e[1me[31mC:\node_modules\jupyterlab-prodigy doesn't existe[39me[22m

webpack 5.31.2 compiled with e[1me[31m1 errore[39me[22m and e[1me[33m1 warninge[39me[22m in 47442 ms

asset e[1me[32mindex.csse[39me[22m 16.1 KiB e[1me[33m[compared for emit]e[39me[22m (name: index)
asset e[1me[32mindex.jse[39me[22m 0 bytes e[1me[33m[compared for emit]e[39me[22m e[1me[32m[minimized]e[39me[22m (name: index)
Entrypoint e[1mindexe[39me[22m 16.1 KiB = e[1me[32mindex.csse[39me[22m 16.1 KiB e[1me[32mindex.jse[39me[22m 0 bytes
e[1m./node_modules/@jupyterlab/theme-dark-extension/style/index.csse[39me[22m 50 bytes e[1me[33m[built]e[39me[22m e[1me[33m[code generated]e[39me[22m
css ./node_modules/css-loader/dist/cjs.js!e[1m./node_modules/@jupyterlab/theme-dark-extension/style/variables.csse[39me[22m 15.3 KiB e[1me[33m[code generated]e[39me[22m
css ./node_modules/css-loader/dist/cjs.js!e[1m./node_modules/@jupyterlab/theme-dark-extension/style/base.csse[39me[22m 472 bytes e[1me[33m[code generated]e[39me[22m
css ./node_modules/css-loader/dist/cjs.js!e[1m./node_modules/@jupyterlab/theme-dark-extension/style/index.csse[39me[22m 342 bytes e[1me[33m[code generated]e[39me[22m
webpack 5.31.2 compiled e[1me[32msuccessfullye[39me[22m in 2024 ms

asset e[1me[32mindex.csse[39me[22m 15 KiB e[1me[33m[compared for emit]e[39me[22m (name: index)
asset e[1me[32mindex.jse[39me[22m 0 bytes e[1me[33m[compared for emit]e[39me[22m e[1me[32m[minimized]e[39me[22m (name: index)
Entrypoint e[1mindexe[39me[22m 15 KiB = e[1me[32mindex.csse[39me[22m 15 KiB e[1me[32mindex.jse[39me[22m 0 bytes
e[1m./node_modules/@jupyterlab/theme-light-extension/style/index.csse[39me[22m 50 bytes e[1me[33m[built]e[39me[22m e[1me[33m[code generated]e[39me[22m
css ./node_modules/css-loader/dist/cjs.js!e[1m./node_modules/@jupyterlab/theme-light-extension/style/variables.csse[39me[22m 14.2 KiB e[1me[33m[code generated]e[39me[22m
css ./node_modules/css-loader/dist/cjs.js!e[1m./node_modules/@jupyterlab/theme-light-extension/style/base.csse[39me[22m 472 bytes e[1me[33m[code generated]e[39me[22m
css ./node_modules/css-loader/dist/cjs.js!e[1m./node_modules/@jupyterlab/theme-light-extension/style/index.csse[39me[22m 342 bytes e[1me[33m[code generated]e[39me[22m
webpack 5.31.2 compiled e[1me[32msuccessfullye[39me[22m in 1924 ms
error Command failed with exit code 1.
info Visit yarn run | Yarn for documentation about this command.

[LabBuildApp] JupyterLab failed to build
[LabBuildApp] Traceback (most recent call last):

[LabBuildApp] File "C:\Users\t724614\Anaconda3\lib\site-packages\jupyterlab\debuglog.py", line 47, in debug_logging
yield

[LabBuildApp] File "C:\Users\t724614\Anaconda3\lib\site-packages\jupyterlab\labapp.py", line 166, in start
raise e

[LabBuildApp] File "C:\Users\t724614\Anaconda3\lib\site-packages\jupyterlab\labapp.py", line 162, in start
build(name=self.name, version=self.version,

[LabBuildApp] File "C:\Users\t724614\Anaconda3\lib\site-packages\jupyterlab\commands.py", line 469, in build
return handler.build(name=name, version=version, static_url=static_url,

[LabBuildApp] File "C:\Users\t724614\Anaconda3\lib\site-packages\jupyterlab\commands.py", line 678, in build
raise RuntimeError(msg)

[LabBuildApp] RuntimeError: JupyterLab failed to build

[LabBuildApp] Exiting application: JupyterLab

I found on another thread that the version of jupyterlab seems to be the issue, so I downgraded to jupyterlab v2.0.0 but then I got this warning:

 jupyter labextension install jupyterlab-prodigy
 An error occured.
 
 Conflicting Dependencies:
 JupyterLab Extension Package
 
 > =3.0.11 <3.1.0 >=2.1.2 <3.0.0 @jupyterlab/application
 > =3.0.9 <3.1.0 >=2.1.1 <3.0.0 @jupyterlab/apputils
 > =3.0.9 <3.1.0 >=2.1.1 <3.0.0 @jupyterlab/launcher
 > =3.0.6 <3.1.0 >=2.1.0 <3.0.0 @jupyterlab/settingregistry

I then updated back to JupyterLab v3.0.0 and when I checked jupyter labextention list I got this:

 JupyterLab v3.0.0
 c:\users\t724614\anaconda3\share\jupyter\labextensions
         @jupyter-widgets/jupyterlab-manager v3.0.0 enabled ok (python, jupyterlab_widgets)
 
 Other labextensions (built into JupyterLab)
    app dir: c:\users\t724614\anaconda3\share\jupyter\lab
         jupyterlab-prodigy v2.0.0 enabled  X
 
    The following extension are outdated:
         jupyterlab-prodigy
 
    Consider running "jupyter labextension update --all" to check for updates.

When I ran jupyter labextension update --all it told me "No compatible version found for jupyterlab-prodigy!"

The docs say JupyterLab v2.0.0 or higher work with prodigy, and yet the build seems to fail. When I try running it with a version older than 3.0.6, it tells me jupyterlab has conflicting dependences. Then when I update to another version, it tells me prodigy doesn't work. What version of jupyterlab should I be using for this to work? Can anyone tell me if there's something in the error log that points to a specific error you've encountered?

Hi! Sorry this is so confusing – for every new version of JupyterLab, we ended up having to publish a new version of the extension. We tried to match the version number of the extension to the version of JupyterLab it's compatible with, so the extension v2.x should be compatible with JupyterLab v2.x, and v3.0 we just released last month should be compatible with JupyterLab v3.x.

So just to confirm, that error "JupyterLab failed to build" happens when you're trying to run JuptyerLab v3.x with the latest version of the Prodigy extension?

Hi Ines, thank you for your response! Apologies for the late reply. Yes I am currently using JupyterLab v3.0.16 and I get "JupyterLab failed to build" when I try to run the command jupyter labextension install jupyterlab-prodigy
which I assume is the latest version of the Prodigy extension. Any help you could provide is much appreciated!

by the way, when i check jupyter labextension list is shows me this:

JupyterLab v3.0.16
c:\users\t724614\anaconda3\share\jupyter\labextensions
        @jupyter-widgets/jupyterlab-manager v3.0.0 enabled ok (python, jupyterlab_widgets)

Other labextensions (built into JupyterLab)
   app dir: C:\Users\t724614\Anaconda3\share\jupyter\lab
        jupyterlab-prodigy v3.0.0 enabled ok


Build recommended, please run `jupyter lab build`:
    jupyterlab-prodigy needs to be included in build

but then when I run jupyter lab build it fails with this error:

An error occured.
RuntimeError: JupyterLab failed to build
See the log file for details:  C:\...\Temp\jupyterlab-debug-hg43mt2n.log

The log file I get is similar to the one I posted in my original question, but looking through it I can't figure out what may be causing the problem

I'm just re-reading the error log again (ugh, Node errors are always so messy) and it looks like it seems to traverse all possible locations of your node_modules, trying to find the installed jupyterlab-prodigy extension and trying out all possible settings that could help it resolve it. But it doesn't seem to find it :thinking:

What happens if you just run npm install jupyterlab-prodigy explicitly?

Hmm is there a specific directory I should be trying to run npm install jupyterlab-prodigy in? It doesn't seem to let me install it in the root directory, I tried in the Anaconda3 folder and that seemed to work but still gives me the jupyterlab failed to build error when I run jupyter labextension install jupyterlab-prodigy or jupyter lab build

So I tried running npm install jupyterlab-prodigy via the Anaconda IDE and it seemed to work, but when I ran the build again it said it failed. The error log looks different now though, I'm not sure if you're able to see anything in it that might give a clue:

Node v14.17.3

Yarn configuration loaded.
> "C:\Program Files\nodejs\npm.CMD" pack jupyterlab-prodigy
npm notice 
npm notice package: jupyterlab-prodigy@3.0.0
npm notice === Tarball Contents === 
npm notice 2.1kB package.json      
npm notice 1.1kB LICENSE.txt       
npm notice 3.0kB README.md         
npm notice 839B  schema/plugin.json
npm notice 942B  style/docs.svg    
npm notice 9.4kB style/icon.png    
npm notice 385B  style/index.css   
npm notice === Tarball Details === 
npm notice name:          jupyterlab-prodigy                      
npm notice version:       3.0.0                                   
npm notice filename:      jupyterlab-prodigy-3.0.0.tgz            
npm notice package size:  11.8 kB                                 
npm notice unpacked size: 17.8 kB                                 
npm notice shasum:        aa24c3c0b698af4d713dc69716ae47a7d32fc010
npm notice integrity:     sha512-FlqZ2P1j88sAn[...]YAubiT3oymS4A==
npm notice total files:   7                                       
npm notice 
jupyterlab-prodigy-3.0.0.tgz

Fetching URL: https://registry.yarnpkg.com/jupyterlab-prodigy
> "C:\Program Files\nodejs\npm.CMD" pack jupyterlab-prodigy@3.0.0
npm notice 
npm notice package: jupyterlab-prodigy@3.0.0
npm notice === Tarball Contents === 
npm notice 2.1kB package.json      
npm notice 1.1kB LICENSE.txt       
npm notice 3.0kB README.md         
npm notice 839B  schema/plugin.json
npm notice 942B  style/docs.svg    
npm notice 9.4kB style/icon.png    
npm notice 385B  style/index.css   
npm notice === Tarball Details === 
npm notice name:          jupyterlab-prodigy                      
npm notice version:       3.0.0                                   
npm notice filename:      jupyterlab-prodigy-3.0.0.tgz            
npm notice package size:  11.8 kB                                 
npm notice unpacked size: 17.8 kB                                 
npm notice shasum:        aa24c3c0b698af4d713dc69716ae47a7d32fc010
npm notice integrity:     sha512-FlqZ2P1j88sAn[...]YAubiT3oymS4A==
npm notice total files:   7                                       
npm notice 
jupyterlab-prodigy-3.0.0.tgz

Node v14.17.3

Yarn configuration loaded.
Building jupyterlab assets (production, minimized)
> node C:\Users\t724614\Anaconda3\lib\site-packages\jupyterlab\staging\yarn.js install --non-interactive
yarn install v1.21.1
warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.
[1/5] Validating package.json...
[2/5] Resolving packages...
success Already up-to-date.
Done in 3.97s.

> node C:\Users\t724614\Anaconda3\lib\site-packages\jupyterlab\staging\yarn.js yarn-deduplicate -s fewer --fail
yarn run v1.21.1
$ C:\Users\t724614\Anaconda3\share\jupyter\lab\staging\node_modules\.bin\yarn-deduplicate -s fewer --fail
Done in 3.11s.

> node C:\Users\t724614\Anaconda3\lib\site-packages\jupyterlab\staging\yarn.js run build:prod:minimize
yarn run v1.21.1
$ webpack --config webpack.prod.minimize.config.js
[webpack-cli] e[31mModuleNotFoundError: Module not found: Error: Can't resolve 'process/browser' in 'C:\Users\t724614\node_modules\@jupyterlab\coreutils\lib'
    at C:\Users\t724614\Anaconda3\share\jupyter\lab\staging\node_modules\webpack\lib\Compilation.js:1672:28
    at C:\Users\t724614\Anaconda3\share\jupyter\lab\staging\node_modules\webpack\lib\NormalModuleFactory.js:712:13
    at eval (eval at create (C:\Users\t724614\Anaconda3\share\jupyter\lab\staging\node_modules\tapable\lib\HookCodeFactory.js:33:10), <anonymous>:10:1)
    at C:\Users\t724614\Anaconda3\share\jupyter\lab\staging\node_modules\webpack\lib\NormalModuleFactory.js:273:22
    at eval (eval at create (C:\Users\t724614\Anaconda3\share\jupyter\lab\staging\node_modules\tapable\lib\HookCodeFactory.js:33:10), <anonymous>:9:1)
    at C:\Users\t724614\Anaconda3\share\jupyter\lab\staging\node_modules\webpack\lib\NormalModuleFactory.js:402:22
    at C:\Users\t724614\Anaconda3\share\jupyter\lab\staging\node_modules\webpack\lib\NormalModuleFactory.js:117:11
    at C:\Users\t724614\Anaconda3\share\jupyter\lab\staging\node_modules\webpack\lib\NormalModuleFactory.js:628:24
    at C:\Users\t724614\Anaconda3\share\jupyter\lab\staging\node_modules\webpack\lib\NormalModuleFactory.js:782:8
    at C:\Users\t724614\Anaconda3\share\jupyter\lab\staging\node_modules\webpack\lib\NormalModuleFactory.js:902:5
resolve 'process/browser' in 'C:\Users\t724614\node_modules\@jupyterlab\coreutils\lib'
  Parsed request is a module
  using description file: C:\Users\t724614\node_modules\@jupyterlab\coreutils\package.json (relative path: ./lib)
    resolve as module
      C:\Users\t724614\node_modules\@jupyterlab\coreutils\lib\node_modules doesn't exist or is not a directory
      C:\Users\t724614\node_modules\@jupyterlab\coreutils\node_modules doesn't exist or is not a directory
      C:\Users\t724614\node_modules\@jupyterlab\node_modules doesn't exist or is not a directory
      C:\Users\t724614\node_modules\node_modules doesn't exist or is not a directory
      looking for modules in C:\Users\t724614\node_modules
        C:\Users\t724614\node_modules\process doesn't exist
      C:\Users\node_modules doesn't exist or is not a directory
      looking for modules in C:\node_modules
        C:\node_modules\process doesn't exist
    aliased with mapping 'process': 'C:\Users\t724614\Anaconda3\share\jupyter\lab\staging\node_modules\process\browser.js' to 'C:\Users\t724614\Anaconda3\share\jupyter\lab\staging\node_modules\process\browser.js/browser'
      using description file: C:\Users\t724614\node_modules\@jupyterlab\coreutils\package.json (relative path: ./lib)
        using description file: C:\Users\t724614\Anaconda3\share\jupyter\lab\staging\node_modules\process\package.json (relative path: ./browser.js/browser)
          no extension
            Field 'browser' doesn't contain a valid alias configuration
            C:\Users\t724614\Anaconda3\share\jupyter\lab\staging\node_modules\process\browser.js\browser doesn't exist
          .js
            Field 'browser' doesn't contain a valid alias configuration
            C:\Users\t724614\Anaconda3\share\jupyter\lab\staging\node_modules\process\browser.js\browser.js doesn't exist
          .json
            Field 'browser' doesn't contain a valid alias configuration
            C:\Users\t724614\Anaconda3\share\jupyter\lab\staging\node_modules\process\browser.js\browser.json doesn't exist
          .wasm
            Field 'browser' doesn't contain a valid alias configuration
            C:\Users\t724614\Anaconda3\share\jupyter\lab\staging\node_modules\process\browser.js\browser.wasm doesn't exist
          as directory
            C:\Users\t724614\Anaconda3\share\jupyter\lab\staging\node_modules\process\browser.js\browser doesn't existe[39m
error Command failed with exit code 2.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

JupyterLab failed to build
Traceback (most recent call last):

  File "C:\Users\t724614\Anaconda3\lib\site-packages\jupyterlab\debuglog.py", line 47, in debug_logging
    yield

  File "C:\Users\t724614\Anaconda3\lib\site-packages\jupyterlab\labextensions.py", line 133, in start
    build(clean_staging=self.should_clean,

  File "C:\Users\t724614\Anaconda3\lib\site-packages\jupyterlab\commands.py", line 469, in build
    return handler.build(name=name, version=version, static_url=static_url,

  File "C:\Users\t724614\Anaconda3\lib\site-packages\jupyterlab\commands.py", line 678, in build
    raise RuntimeError(msg)

RuntimeError: JupyterLab failed to build

Exiting application: lab

Yay, at least this looks like progress :sweat_smile:

I think you can just run npm install from anywhere and it'll install the package into your global node modules (kinda like how Python installs into the system Python by default). You can also run npm init to make your current working directory an npm project, and then install with npm install --save to install the packages into a node_modules the local directory (which is more like a virtual environment in Python, I guess). But I think the way you did it is totally fine.

This looks more like a general Node/Webpack/JupyterLab issue now :thinking: I googled it and everything I found was mostly around Node compatibility, so I wonder if maybe upgrading Node helps? Can you check node --version and see what you have? If this looks old (lower than 10 or 11), maybe you could try upgrading Node.

I was thinking it might be a webpack issue as well too, but I wasn't sure what that would mean exactly. My version of Node is up to date at v14.17.3

Hmm, strange – I wish I could be more helpful! I was looking around and found a reference to a fix related to process/browser in the changelog for v3.1.0b2 of JupyterLab here: JupyterLab Changelog — JupyterLab 3.1.0rc1 documentation So maybe you could try and upgrade JupyterLab and see if that helps?

@emilyboss , did you ever find a solution to this? I'm having the same issue.

1 Like

same issue here

1 Like

no :pensive: but i haven't had too much time to work with it the last week, so i will update this thread if i figure anything out! let me know if you get somewhere with it :slight_smile:

Hey Ines, same problem here with command 'jupyter lab build --dev-build=False --minimize=False' Could you please have a look at the error log?


Having the same problem here with prodigy 1.11, jupyterlab 3.1.9 and nodejs v16.6.1. I have a version working (with some hacks) for prodigy 1.10.7, jupyterlab 2.2.6 and nodejs v15.12.0. Unlike emilyboss though the npm install command doesn't seem to change anything for me. I can definitely add other jupyterlab extensions and compile the installation fine, it's just something with this extension which is causing me problems. Can I revert to the same jupyterlab version I am using for my older Prodigy version or are there dependencies on the newer v3? Earlier posts would suggest this doesn't work, but just double checking I've understood correctly!

Has anyone found a solution yet?

I have the exact same problem as Emily

I have found a solution to my problem.

Apparently I had to use jupyterlab>=2.0.0,<3.0.0. For some reason I had not seen this part before posting and so I spent the whole day getting the errors described above.

@PINS_1 if you are still working with Jupyterlab, just downgrade your version and then it should work

I hope this will help someone as well.

Hi @Zim1-finest , sorry for taking a while. Yes, I can confirm that that is indeed the solution. The README has already been updated. For those who have conflicting dependencies, I highly recommend installing it in a clean environment (a virtualenv, etc.).

We're currently in the process of releasing a Jupyterlab>=3.0 compatible extension, so stay tuned!

Hi folks,

We just released a new version of jupyterlab-prodigy (4.0.0). It is now compatible with newer versions of Jupyterlab (>=3.0.0). You can try it out by running:

pip install jupyterlab-prodigy

For older Jupyterlab versions (>=2.0.0, <3.0.0), install jupyterlab-prodigy@3.0.0:

jupyter labextension install jupyterlab-prodigy@3.0.0

If you encountered any bugs or questions, feel free to open an Issue / Discussion here or at the Github page.

3 Likes