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
Activate the deferred plugins after shell restore #14610
Conversation
Thanks for making a pull request to jupyterlab! |
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.
Thanks @brichet
I have some comments and I think we should wait for a new release of lumino with the related change. As the behavior of deferred extensions is gonna changed, I would prefer to have it in a new minor version.
Test failure does not appear to be linked to this PR. |
551a3eb
to
d763592
Compare
Co-authored-by: Frédéric Collonval <fcollonval@users.noreply.github.com>
Co-authored-by: Frédéric Collonval <fcollonval@users.noreply.github.com>
… add tests on plugin activation
388c9e2
to
3f163d6
Compare
Thanks @brichet merging this one now. |
This PR improves pageload time by deferring the activation of huge extensions.
After the shell restore, activates the plugins that have been deferred from:
page_config.json
, currently they are not activated at all if not required by another plugindeferred
coming from Add a 'defer' option to the autoStart argument lumino#588References
Fixes #14576
Related to jupyterlab/lumino#588
Code changes
The changes are in
JupyterLab
class.User-facing changes
Activation of a plugin containing a 5s sleep:
Backwards-incompatible changes
This is currently backward compatible but I used
// @ts-ignore
to avoid error at compilation.There may be better implementation for it.