Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[DEV] use latest jupyterlab APIs #268

Merged
merged 3 commits into from
Oct 19, 2020
Merged

Conversation

minrk
Copy link
Collaborator

@minrk minrk commented Oct 17, 2020

updates everything except for webpack 5, which doesn't seem to work yet. This uses the packages from the latest jupyterlab 3.0 release candidate.

The changes are relatively small:

  • use KernelManager().startNew instead of Session.startNew
  • appendToken behavior is now opt-in instead of the default. This is required for cross-origin use cases like ours
  • no longer accepts partial serverSettings, only filled-out by makeSettings

This seems to work just fine, but I don't want to introduce any conflicts with what other sprinters are working on

shim(/@phosphor\/collections\/lib\/(bplustree).*/),
shim(/@phosphor\/(dragdrop|commands).*/),
shim(/@lumino\/collections\/lib\/(bplustree).*/),
shim(/@lumino\/(dragdrop|commands).*/),
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The shims will need revisiting, as the bundle got even bigger again!

not ready for webpack 5, but everything else is updated
mainly:

- lumino imports
- fill out partial serverSettings with makeSettings
- opt-in to appendToken (previously default behavior)
- switch from Session.startNew to KernelManager().startNew
it's huge, but seems required for widget-output at least
@minrk minrk marked this pull request as ready for review October 19, 2020 08:54
@minrk minrk changed the title [WIP] use latest jupyterlab APIs [DEV] use latest jupyterlab APIs Oct 19, 2020
@minrk
Copy link
Collaborator Author

minrk commented Oct 19, 2020

This is working, and should no longer conflict with sprint contributions

@minrk minrk merged commit f55f618 into jupyter-book:master Oct 19, 2020
@minrk minrk deleted the jupyterlab-bumps branch October 19, 2020 08:56
@choldgraf
Copy link
Collaborator

@minrk will this be an issue if JupyterLab isn't installed on the particular binder instance that a person requests? E.g. I think that Binder ships with JupyterLab 2.X right now, and I dunno when it'll switch to 3.x

@minrk
Copy link
Collaborator Author

minrk commented Oct 22, 2020

It shouldn't. This only means the jupyterlab javascript APIs that are pulled in as part of thebe itself. It should not be sensitive to the server-side version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants