-
Notifications
You must be signed in to change notification settings - Fork 505
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
Follow-up on #846 #1243
Comments
We should also consider updating to the latest Updating the top post to add this item. |
Please, whatever happens, make CDN opt-in, providing a robust way to serve a known list of locally-available extensions, so that a they can be deployed along with a voila deployment. Reliance on (or having to co-deploy) a CDN is the cause of many issues when trying to actually own a non-public jupyter stack, and the well-understood scope and directory layout of prebuilt labextensions makes it far easier to manage than the previous requirejs mess. To account for versioning, it might even be possible to serve directly from a pile of not-installed
Yes. Encouraging folk to author in a theme environment consistent with their deployment is huge. |
Just adding a note that jupyterlab themes are actually already supported :D Though we don't support yet dynamically switching themes in the front-end. |
That's probably good for most deployment use cases. |
Closing as |
Reposted from #846
nbconvert
: https://github.com/jupyter/nbconvert/blob/957c2e2476e1106fd4976af7d104c01cd5bb7562/setup.py#L52-L56The text was updated successfully, but these errors were encountered: