Installation freezes on Resolving packages... @oriolmirosa/jupyterlab_materialdarker@file:../extensions/oriolmirosa-jupyterlab_materialdarker-0.3.0.tgz

[ivan-rivera]

After running jupyter labextension install @oriolmirosa/jupyterlab_materialdarker the installation appears to freeze after about a minute. Here is the log:

jupyter labextension install @oriolmirosa/jupyterlab_materialdarker                                                             
> /usr/local/bin/npm pack @oriolmirosa/jupyterlab_materialdarker
npm notice
npm notice 📦  @oriolmirosa/[email protected]
npm notice === Tarball Contents ===
npm notice 1.6kB   package.json
npm notice 546B    README.md
npm notice 193B    lib/index.d.ts
npm notice 664B    lib/index.js
npm notice 120.5kB static/43bb4cbf1d0ecfdb1309e4cb67264f35.ttf
npm notice 120.5kB static/5a0856eb52623ae94b09dbbf31a27b95.ttf
npm notice 67.3kB  static/index.css
npm notice === Tarball Details ===
npm notice name:          @oriolmirosa/jupyterlab_materialdarker
npm notice version:       0.3.0
npm notice filename:      oriolmirosa-jupyterlab_materialdarker-0.3.0.tgz
npm notice package size:  132.7 kB
npm notice unpacked size: 311.3 kB
npm notice shasum:        464b4a2d4f14e9f1b27dcfda43d2af473a4eab65
npm notice integrity:     sha512-AXb7J2FcgaBJr[...]kBT5W0mGuCC1A==
npm notice total files:   7
npm notice
oriolmirosa-jupyterlab_materialdarker-0.3.0.tgz
> node /anaconda3/lib/python3.6/site-packages/jupyterlab/staging/yarn.js install
yarn install v1.5.1
(node:6932) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
info No lockfile found.
[1/4] 🔍  Resolving packages...
⠈ @oriolmirosa/jupyterlab_materialdarker@file:../extensions/oriolmirosa-jupyterlab_materialdarker-0.3.0.tgz

I've given it over an hour to finish before giving up. Now every time I launch jupyter lab it's saying "@oriolmirosa/jupyterlab_materialdarker needs to be included in build" and asks me to start the build process.

Any suggestions on how I might fix this?

Many thanks!

[oriolmirosa]

Are you on node 10? There are reports of this happening with jupyterlab extensions if node 10 is installed. Downgrade to a node 9 version and try again. Let me know if this is still happening then.

[ivan-rivera]

Had to downgrade to node 8 and then I managed to install it. But then I ran into another issue -- after launching jupyter and selecting this theme, I got an error in my browser:

Error Loading Theme -- Stylesheet failed to load: /lab/api/themes/MaterialDarker/index.css

I was then unable to interact with the page and the only way to recover jupyter was to uninstall this extension.

[oriolmirosa]

Hmm... I have only seen a problem like this when I have tried to install the extension on a jupyterhub instance and I had issues with user permissions. Are you installing this on your own system? What is the application directory in jupyter lab path (the first on the list)? Do you have permissions to access it? If you do, I suggest that you manually delete the extension from the extensions folder in the application directory and reinstall from scratch. Let me know what happens.

[ivan-rivera]

Yep, I'm installing it on my system. The application directory you were wondering about is /anaconda3/share/jupyter/lab and I do have permissions to access it, I was running the installation in sudo mode.

[oriolmirosa]

That might be the issue. If you install with sudo the path is probably different and you have a permission issue. Did you install anaconda as root? That can lead to problems. See the last comment in this thread:

conda/conda#6638

[universvm]

I am not sure if it can help, but I am not using anaconda and I am having the same problem.

[oriolmirosa]

@universvm, what version of Node are you using?

[universvm]

@oriolmirosa I was using 10.3 but even after updating to 10.6 the problem persists.

[oriolmirosa]

@universvm As I mentioned earlier in the thread, this is a known problem of jupyterlab with Node 10. If you downgrade to Node 9 the problem should go away. Can you give it a try?

[universvm]

@oriolmirosa I can't downgrade unfortunately as I am on a work laptop. Is there really no alternative?

Could you also provide a solution to the following problem, I can't seem to get rid of this error message...

[oriolmirosa]

@universvm The build message would disappear if you were able to install the extension. As far as I know, the original problem is a general issue with jupyterlab, which is not unexpected given that jupyterlab is still in beta. I saw that the first release candidate of jupyterlab 0.33 was pushed a few days ago, so you could install that (or wait until the official 0.33 release soon) to see if the issue with node 10 is fixed.

[kurakuradave]

Hi, I managed to install it and set my color theme, however that "Build Recommended" message appears every time I started jupyterlab.. any ideas? thanks
I'm on Ubuntu 16.04, python 3.5.2 and jupyter lab 0.32.1

[thgngu]

Everyone,

I had a similar issue with another jupyterlab extension (before I come to this extension). This comment helps me fix the problem without downgrading my node 10.

I'm on Ubuntu 16.04, Anaconda 4.5.8, Python 3.6, Jupyterlab 0.32.1

[joshbode]

Thanks @thongnnguyen :)

This worked for me with no downgrade of node required:

$ npm install -g yarn
/Users/josh/.local/bin/yarnpkg -> /Users/josh/.local/lib/node_modules/yarn/bin/yarn.js
/Users/josh/.local/bin/yarn -> /Users/josh/.local/lib/node_modules/yarn/bin/yarn.js
+ [email protected]
updated 1 package in 0.485s

$ yarn config set yarn-path "$(which yarn)"
yarn config v1.9.2
success Set "yarn-path" to "/Users/josh/.local/bin/yarn".

$ jupyter labextension install @oriolmirosa/jupyterlab_materialdarker

macOS 10.13.6, Node v10.7.0 (via brew), Python 3.7.0 (via brew), JupyterLab 0.33.4 (via pip)

[oriolmirosa]

Jupyterlab 0.34 contains this change:

• JupyterLab now uses yarn 1.9.4 (aliased as jlpm), which now allows users to use Node 10+. (#5121).

This issue should be resolved then. Please feel free to re-open if the problems continue.

Thanks everyone!