There is no "Enable Extensions Manager" !

[NILICK]

I installed latest version of JupyterLab App v3.1.13-1 but there is not "Enable Extensions Manager" option in setting menu. I then run jupyter labextension install @jupyter-widgets/jupyterlab-manager but I have same problem.

JupyterLab v3.1.13
/opt/JupyterLab/resources/jlab_server/share/jupyter/labextensions
        @bokeh/jupyter_bokeh v3.0.2 enabled OK (python, jupyter_bokeh)
        @pyviz/jupyterlab_pyviz v2.1.0 enabled OK (python, pyviz_comms)
        @jupyter-widgets/jupyterlab-manager v3.0.1 enabled OK (python, jupyterlab_widgets)

Other labextensions (built into JupyterLab)
   app dir: /opt/JupyterLab/resources/jlab_server/share/jupyter/lab
        @ijmbarr/jupyterlab_spellchecker v0.7.1 enabled OK
        @jupyter-widgets/jupyterlab-sidecar v0.6.1 enabled OK
        jupyter-leaflet v0.14.0 enabled OK

[mbektas]

Installing additional JupyterLab Extensions are not supported in the desktop application at the moment. We are considering adding this support in a future release.

[dirkroorda]

That means: no vim bindings in code cells. That means: although the desktop app is a big improvement for getting started with jupyter notebooks for users that do not have Python yet, I will not use it for work right now. Otherwise, there is much to like about having JLab is an app!

[krassowski]

Please note that prebuilt extensions are now supported since 3.2.1-2 and can be installed via pip or conda, but extension manager is still disabled as it does not support installation of prebuilt extensions yet.

[hellojinwoo]

@krassowski If the installation is possible only with the command jupyter labextension install, can't I install the extension? For example, when it comes to the jupyterlab theme city-lights, the only provided installation command is as follows:

jupyter labextension install @yudai-nkt/jupyterlab_city-lights-theme

Can't I install this theme on the Jupyterlab Desktop app because it is not installed via pip nor conda?

Theme repo: https://github.com/yudai-nkt/jupyterlab_city-lights-theme

[krassowski]

jupyter labextension install is a command for installing source extensions which is the old way of distributing extensions. Only prebuilt extensions are supported in JupyterLab Desktop. You can read more on different types of extensions in JuptyterLab documentation (installing extensions, overview of extensions).

The installation of source extensions is likely to be removed in future versions of JupyterLab: https://github.com/jupyterlab/jupyterlab/issues/11336 so any extensions that have not migrated should start migration now.

[d2weber]

I noticed that the extension manager indeed shows up, after the following steps:

• Help > Open Developer Tools
• Close developer tools by clicking on 'x'
• Clicking the button "Skip to left Sidebar", which appeared

After clicking that button the Extensions Manager is visible. It seems also that other adjustments made in the desktop version vanished, for example the help menu is like the normal one. I'm using Ubuntu 20.04.

@dirkroorda Maybe an alternative to jupyterlab-desktop might be this: Using a normal jupyterlab installation but configure it so that chrome/chromium starts it in app-mode, hence without menubar.

[krassowski]

These steps should not be used to access Extension Manager - we do not support the Extension Manager for the reasons stated above (and more). You are essentially loading a different application (the plain JupyterLab which is shipped underneath) instead of the Desktop version.

[meeseeksmachine]

This issue has been mentioned on Jupyter Community Forum. There might be relevant details there:

https://discourse.jupyter.org/t/jupyterlab-windows-app-missing-extension-manager/11614/2

[dirkroorda]

I installed the newest JupyterLab app. It says it can now use prebuilt extensions, i.e. the ones installed with pip. jupyterlab-vim is such an extension. Yet it does not work. It is as if it is not there. If I do a pip install jupyterlab-vim within a notebook, it says that the requirement is already satisfied.

Yet, if I do an intricate sequence of reinstalling jupyterlab-vim, restarting the kernel, refreshing the page, opening another notebook, then I do see the extension in action. Here is proof:

Now I have to find out what the minimum action is to get vim in notebook cells.

When I restart the JupyterLab app, the effect of jupyterlab-vim is gone initially. But if I then do a refresh (Cmd-R), the extension is active in all open notebooks.

Not bad at all, in fact. Even workable.

But a bit rough still.

[krassowski]

@dirkroorda please do open a new bug report issue describing exactly how you installed it (%pip, !pip, conda; into which environment, how the environment was created), which version you have in Help → About, and all output from browser console and terminal.

[dirkroorda]

Macos 11.6.1; Safari. Fresh install of Jupyterlab app 3.2.5-1.

I did both the bundled Python environment and the system python environment.

My /usr/local/bin/python3 is this one: Python 3.10.0 (v3.10.0:b494f5935c, Oct 4 2021, 14:59:20) [Clang 12.0.5 (clang-1205.0.22.11)] on darwin

In the bundled environment I did this in a code cell:

pip install jupyterlab-vim

In my system python jupyterlab-vim was already installed.

[krassowski]

This would not work in the bundled environment without changing ownership of the directory, and again depending on whether you used %pip or !pip it would or would not work. Please refer to the user guide: https://github.com/jupyterlab/jupyterlab-desktop/blob/master/user-guide.md#customizing-the-bundled-python-environment.

If the extension does not work on the first try but works after that I would still kindly ask you to fill in the full bug report template please so we can see the logs from the browser and terminal.

[dirkroorda]

@krassowski Sorry, I forgot to mentioned that I installed JupyterLab "for this user only".

And I did neither %pip, nor !pip, but just pip.

Both in the system environment as well as in the bundled environment I had the same effects: initially jupyterlab-app does not see the effect of the installed package, but only after a refresh and/or a reopening of the notebook.

I do not know what more information to collect.

**Update: see issue #379 **