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

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

Open
jtpio opened this issue Nov 6, 2024 · 1 comment
Open

Comments

@jtpio
Copy link
Member

jtpio commented Nov 6, 2024

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

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 #7354 (comment)

@jupyterlab-probot jupyterlab-probot bot added the status:Needs Triage Applied to issues that need triage label Nov 6, 2024
@jtpio
Copy link
Member Author

jtpio commented Nov 6, 2024

#7513 already seems to be helping with the most common caching issues. So we could postpone that issue to the next 7.4.0 milestone.

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

No branches or pull requests

2 participants