KeyError: '@jupyterlab/apputils' when installing voyager?
See original GitHub issueHi there, I failed to install jupyterlab_voyager running jupyter labextension install jupyterlab_voyager
as showed in README.md. It shows 'KeyError:
@jupyterlab/apputils’`.
I can install other extensions like toc and go-to-definition. How can I fix it? THANKS.
Issue Analytics
- State:
- Created 4 years ago
- Comments:12
Top Results From Across the Web
Basemap library using Anaconda Jupyter Notebooks - KeyError
I'm trying to install and import the Basemap library into my Jupyter Notebook, but this returns the following error: KeyError: 'PROJ_LIB'.
Read more >@jupyterlab/apputils - npm
A JupyterLab package which provides a collection of utilities and UI elements for building an application and manipulating the DOM. Keywords.
Read more >How to Connect to JupyterLab Remotely | by Luke Gloege, Ph.D.
This post will walk you through how to launch Jupyterlab on a SLURM cluster and then connect from a browser running on your...
Read more >Installation — JupyterLab 3.6.0b0 documentation
If installing using pip install --user , you must add the user-level bin directory to your PATH environment variable in order to launch...
Read more >jupyterlab-plugin-playground - PyPI
pip install jupyterlab-plugin-playground ... import { ICommandPalette } from '@jupyterlab/apputils'; const plugin = { id: 'my-super-cool-toggle:plugin', ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@dfdf Hi, this extension has only been tested with jupyterlab 1.0.4 – please use with this version, as we may have to perform updates to use with 1.1.0
@JamesSample Ah, sorry I misread your original issue. I thought you meant the Docker image would not build at all. I also saw the sidebar issue after running the container…i’m not sure why this could be occuring. when i originally tested it these issues weren’t occuring…I can only assume now the best option would be to potentially downgrade to 1.0.2 (as it seems from the referenced issue that could fix it) and in the meantime we will work on upgrading for jupyter 1.1.1
I currently have a working version using https://hub.docker.com/r/jupyter/all-spark-notebook but i haven’t rebuilt the image for a few weeks…