Jeremy Tuloup

Not sure there has been any updates on this since. I moved the issue to the `4.3.x` so it's on the radar, as it could be released as a bug...

Thanks @agriyakhetarpal for the suggestion 👍 Indeed the numpy website currently links to this demo deployment. If I recall correctly this was mostly for convenience. In https://github.com/numpy/numpy.org/pull/557 it was suggested...

> having a shared deployment for Scientific Python could make sense. That sounds like a good tradeoff. One of the main drawbacks of depending on https://jupyterlite.github.io/demo for downstream demos is...

> Waiting for [the upstream change to export the `ContentProviderRegistry` class](https://github.com/jupyterlab/jupyterlab/pull/17940) before making the PR ready for review @martinRenou this should now be available after the update to the latest...

@martinRenou just checking if this PR was still on the radar for 0.7? Or if https://github.com/jupyterlab/jupyterlab/issues/18029 would need to be fixed first?

> @martinRenou just checking if this PR was still on the radar for 0.7? Or if [jupyterlab/jupyterlab#18029](https://github.com/jupyterlab/jupyterlab/issues/18029) would need to be fixed first? Bumping to `0.8.0` then.

Thanks @RensDimmendaal! This list of features is a bit confusing, because not everything is implemented yet. I guess it's a bit confusing because the line above says: > The goal...

FYI @martinRenou https://github.com/jupyterlite/jupyterlite/pull/1819 updated to JupyterLab 4.5.1, which should help unblock this PR.

> Now that I think of it, adding this Dependabot configuration would also add it for everyone who uses this template, which I can see many users might not like,...