Update to JupyterLab 3.0

[jtpio]

Replaces #101

Fixes #100

For now commenting out some extensions that have not been updated yet.

Can be tested with this link: https://mybinder.org/v2/gh/jupyterlab/jupyterlab-demo/lab3?urlpath=lab

TODO

• Update to JupyterLab 3.0
• ipyleaflet
• bqplot
• jupyterlab-renderers
• Check the predefined workspace is correctly restored

[jtpio]

Node 14 is giving the following:

Trying with Node 12 instead.

[jasongrout]

I'm updating the docs to use https://mybinder.org/v2/gh/jupyterlab/jupyterlab-demo/8f2ecb6?urlpath=lab/tree/demo in jupyterlab/jupyterlab#9546

[jasongrout]

After a few seconds on that image, I get this dialog:

Build Recommended
JupyterLab build is suggested:

jupyter-offlinenotebook needs to be included in build

Can we remove that plugin too, or rebuild as part of the image?

[jasongrout]

Can we remove that plugin too, or rebuild as part of the image?

I can't see where we are pulling in that extension. Is it part of the base binder image?

[manics]

I can't see where we are pulling in that extension. Is it part of the base binder image?

Yes, it's in the default repo2docker scripts. I'm going to update it to a new version that works with both JL 2 and 3, and use the new pre-built extensions system so it won't require a rebuild for JL3.

[jtpio]

Yes it is part of the base image and installed here:

https://github.com/jupyterhub/repo2docker/blob/560b1d96a0e39cb8de53cb41a7c2d8d23384eb82/repo2docker/buildpacks/conda/install-miniforge.bash#L60

When the switch to JupyterLab 3.0 is done in repo2docker (jupyterhub/repo2docker#996) this should normally not be an issue anymore since the offline notebook extension will be prebuilt.

[jtpio]

Wondering why the popup still shows up though, since there should also be an explicit build right after:

https://github.com/jupyterhub/repo2docker/blob/560b1d96a0e39cb8de53cb41a7c2d8d23384eb82/repo2docker/buildpacks/conda/install-miniforge.bash#L61

[jasongrout]

Probably because it is never incorporated into lab 3 or something?

We could install the newest version of that package, which supports jlab 3 now (as of an hour ago, 0.2.0 was published)

[jtpio]

The latest commit explicitly installs jupyter-offlinenotebook for now to avoid having the popup:

https://mybinder.org/v2/gh/jupyterlab/jupyterlab-demo/3818244?urlpath=lab

[jasongrout]

https://mybinder.org/v2/gh/jupyterlab/jupyterlab-demo/3818244?urlpath=lab

I updated jupyterlab/jupyterlab#9546 to use this new link

[jtpio]

Looks good with the jupyterlab renderers:

I think it's mostly bqplot left now. Linking to the PR for reference: bqplot/bqplot#1222

[jtpio]

Also it seems like the Binder doesn't open with the predefined workspace anymore.

So something to have a look at too, also to make sure it's not a regression.

[jtpio]

For anyone willing to test the latest changes, here is the link to the Binder for this PR:

https://mybinder.org/v2/gh/jupyterlab/jupyterlab-demo/lab3?urlpath=lab

[jtpio]

To answer your question @SylvainCorlay, this syntax installs 0.10.1:

[jtpio]

Also it seems like the Binder doesn't open with the predefined workspace anymore.

This issue might be relevant: jupyterlab/jupyterlab#9186

[jtpio]

Just added bqplot back, this is starting to look good.

Apart from the workspace restoration issue mentioned above, everything should work as before.

We might also want to remove jupyter-offlinenotebook=0.2 from the repo once it is part of repo2docker by default: jupyterhub/repo2docker#997 (this could be a separate PR)

[jtpio]

Apart from the workspace restoration issue mentioned above, everything should work as before.

Just opened jupyterlab/jupyterlab#9590 as it looks like there might be an issue with the restorer?

[jtpio]

Marking as ready for review, so the workspace issue could be addressed separately.

Instead, we can update the URL to open the Lorenz.ipynb notebook by default using the following link:

https://mybinder.org/v2/gh/jupyterlab/jupyterlab-demo/lab3?urlpath=lab/tree/demo/Lorenz.ipynb

[saulshanabrook]

This looks good to me!

I tried out this branch and seems good.

I agree with @jtpio, to merge this and not block on the upstream JupyterLab 3.0 workspace issue (jupyterlab/jupyterlab#9590).

[blink1073]

I agree, thanks @saulshanabrook!