Stuck resolving packages

[dacowan]

Attempting to install hub_extension and I'm stuck resolving packages (left it running for over a day and it never seems to complete)

` jupyter labextension install @jupyterlab/hub-extension

/usr/local/bin/npm pack @jupyterlab/hub-extension npm notice npm notice 📦 @jupyterlab/[email protected] npm notice === Tarball Contents === npm notice 907B package.json npm notice 1.5kB README.md npm notice 1.5kB LICENSE npm notice 2.5kB lib/index.js npm notice 351B lib/index.d.ts npm notice === Tarball Details === npm notice name: @jupyterlab/hub-extension npm notice version: 0.9.0 npm notice filename: jupyterlab-hub-extension-0.9.0.tgz npm notice package size: 3.0 kB npm notice unpacked size: 6.8 kB npm notice shasum: e92025d314e94d85e786cb5a53e9713edcfd344f npm notice integrity: sha512-kixPpDW+yOAzM[...]ANSCiX4Z1gobQ== npm notice total files: 5 npm notice jupyterlab-hub-extension-0.9.0.tgz node /anaconda/envs/py35/lib/python3.5/site-packages/jupyterlab/staging/yarn.js install yarn install v1.5.1 (node:92840) [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... `

Any suggestions as to how to proceed?

[liffiton]

This only stands a small chance of being relevant, but I had a similar issue when running jupyter lab build -- it would freeze while resolving packages with jupyterlab-hub-extension listed as the current package. I didn't figure out what was causing it, but it worked if I ran the same command as root. I had been running it as a regular user, and all of the relevant files were owned by that user, as far as I knew. It didn't make much sense to me, but like I said, there's a small chance that's relevant here.

[vanpelt]

This seems to be an issue with node 10. I was able to get it to install fine with node 8. v0.9.1 is busted in all versions of node.

[liffiton]

So it looks like an incompatibility with yarn in particular.

jupyter lab build uses yarn, and its current version bundles yarn v1.5.1. But that version doesn't work well with Node 10. I think jupyterlab/jupyterlab#4585 is the most relevant issue. A fix (upgrading the version of yarn bundled with jupyterlab) should come with the next jupyterlab release, and for now, upgrading yarn in place is a workaround that worked for me.