nebari-dev / nebari-dev/data-science-pack
Fix JupyterLab extension version warnings in data science pack image
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5
- Forks
- 7
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 13
Description
When Nebi is loaded through the nebari-data-science-pack JupyterLab image, the browser console shows warnings/errors from JupyterLab frontend extensions.
The image currently runs JupyterLab 4.6.2, but some installed extensions appear to have been built against JupyterLab 4.7.0 prerelease frontend packages. This causes runtime warnings about mismatched shared package versions.
Proposed fix:
- Identify exact extensions via the console remoteEntry sources.
- Rebuild Nebari-owned extensions with a newer jupyter-builder where applicable.
- Correct
package.jsondependency ranges if they incorrectly require newer JupyterLab packages. - Update/pin extension versions in images/jupyterlab/pixi.toml and refresh the lockfile.
- Rebuild the JupyterLab image and verify the console warnings are gone.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the console remoteEntry sources to identify the affected extensions, then inspect their package.json dependency ranges and images/jupyterlab/pixi.toml. Rebuild or update the specified extensions, refresh the lockfile, rebuild the JupyterLab image, and verify that the browser console no longer reports shared-package version warnings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter, python
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100