jupyter / jupyter/notebook

Have one build per page, and use `disabledExtensions` to filter plugins

Open
#7,516 1 comment 0 reactions 0 assignees View on GitHub
maintenance
Dominant language
Jupyter Notebook
Stars
13.3k
Forks
5.8k
Avg merge
6d 11h
Merged PRs (30d)
7

Description

We should consider restructuring the build so each page has its own app and bundle, similar to the approach taken in JupyterLite:

- https://github.com/jupyterlite/jupyterlite/tree/main/app/tree
- https://github.com/jupyterlite/jupyterlite/tree/main/app/consoles
- https://github.com/jupyterlite/jupyterlite/tree/main/app/notebooks

Instead of the current approach which currently builds a single bundle, and activate a specific list of plugins on each page.

_Originally posted by @jtpio in https://github.com/jupyter/notebook/issues/7354#issuecomment-2115199032_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.