latest
version of this page: https://jupyterlab.readthedocs.io/en/latest/developer/extension_dev.html
import { ReactWidget } from '@jupyterlab/apputils';
Thanks for all the quick replies btw, y'all are awesome!
Question regarding handleComms
based on #6929. Suppose the following scenario:
widget-1, widget-2
) of the same widgets are created (e.g. console), each with a different session pointing to two different kernelswidget-1
) to use the session of widget-2
. This closes all comms that was registered by widget-1
since the new kernelconnection does not handleComms
so the registerCommTarget
call will be fenced by an if statement.My question is suppose I want the kernel to talk to the two widgets
(now connected to the same kernel) either simultaenously or independently of each other, how would I send data over since widget-2
now has no Comm associated with it?
widget-1
to handleComms
to keep both comms open?
Hi everyone, I'm running into an issue with extensions that I was hoping someone has a suggestion.
I am running jupyterlab inside a docker container, where I pre-install jupyterlab and all of the extensions as root user. When I run the docker container, I am running as a different user. In this case, the extensions fail to load in jupyterlab because the NPM cache folder is read-only for the current user, with "[...] are not valid NPM packages."
This is actually happening because jupyterlab calls "npm pack" on the extensions, requiring r/w access to the cache. If I chmod the cache first, everything works.
Is there a way to run jupyterlab where this wouldn't be an issue, i.e. it doesn't require r/w access to the original npm cache (that is owned by root on my system)?
@mc-allen have you tried install nodejs within a conda environment? if you have r/w access to the conda/envs dir then you should be fine in that case
package.json
and run yarn why <foo>
in the <app>/staging
directory.