-
Notifications
You must be signed in to change notification settings - Fork 66
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
Conversation
shim(/@phosphor\/collections\/lib\/(bplustree).*/), | ||
shim(/@phosphor\/(dragdrop|commands).*/), | ||
shim(/@lumino\/collections\/lib\/(bplustree).*/), | ||
shim(/@lumino\/(dragdrop|commands).*/), |
There was a problem hiding this comment.
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
18d18c4
to
4abe8bc
Compare
it's huge, but seems required for widget-output at least
4abe8bc
to
e2886e6
Compare
This is working, and should no longer conflict with sprint contributions |
@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 |
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. |
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:
KernelManager().startNew
instead ofSession.startNew
appendToken
behavior is now opt-in instead of the default. This is required for cross-origin use cases like oursThis seems to work just fine, but I don't want to introduce any conflicts with what other sprinters are working on