Jupyter Storage Explorer launcher
Adds Storage Explorer to JupyterLab's launcher (section Other) and command palette. It opens Jupyter Storage Explorer in its own tab, with a kernel of its own that stops when the tab is closed.
The tab opens on the launcher's folder: the one JupyterLab's file browser showed when the launcher was opened (like the
launcher's Notebook and Console items; open a new launcher after changing folder). From the command palette, it opens
on the folder the file browser shows. When the page is reloaded, JupyterLab restores the tab and the explorer is shown
again, from a new run of launch() in the same kernel.
pip install jupyter-storage-explorer-launcher
Install it in the environment of JupyterLab and of the default kernel (on JupyterHub, usually the single-user image),
then restart JupyterLab. It installs jupyter-storage-explorer too.
What the tab shows is set by a file storage-explorer/launcher.py in a Jupyter configuration directory: its launch()
function returns the widget. For example, for one user, ~/.jupyter/storage-explorer/launcher.py:
from jupyter_storage_explorer import StorageExplorer
def launch():
return StorageExplorer(
# "." is the folder the tab opens on (see above)
filesystems={"Here": ".", "Data lake": "abfs://lake@myaccount.dfs.core.windows.net"},
height="fill", # as tall as the tab
)
Administrators can put one in /etc/jupyter/storage-explorer/launcher.py (or <environment>/etc/jupyter/...) for
everyone. The directories are searched in Jupyter's usual order (jupyter --paths, config section) and the first file
found is used. Without one, the tab shows an explorer of the folder it opens on.
The file may also have a style() function returning CSS (without <style>), e.g. to customize the explorer's icons
(see Customizing icons). It applies to the whole JupyterLab page while the tab is
open:
def style():
# Top-level folders in blue instead of yellow
return '.jse-browser [data-depth="1"] .jse-icon { filter: hue-rotate(180deg); }'
Requires JupyterLab 4.
Metadata
Release files for jupyter-storage-explorer-launcher 0.0.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| jupyter_storage_explorer_launcher-0.0.6.tar.gz | 54.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| jupyter_storage_explorer_launcher-0.0.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 82.3 kB
Release files / jupyter_storage_explorer_launcher-0.0.6.tar.gz
| Download URL | jupyter_storage_explorer_launcher-0.0.6.tar.gz |
|---|---|
| Size | 54.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
618ff378b1a6242e2afee7b035cb2fdfe843958631e74be9e40f22e490f0515c
|
|
BLAKE2b-256 checksum How to use checksums |
bca16fcf46dcefc3f58ff0d39ee098907346ca7fcfe1564bd99615e12df0c460
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 10, 2026.
Transparency logRelease files / jupyter_storage_explorer_launcher-0.0.6-py3-none-any.whl
| Download URL | jupyter_storage_explorer_launcher-0.0.6-py3-none-any.whl |
|---|---|
| Size | 27.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
209c04ef452a906e6b14cc07a3e61f3b9690c62aded767de21ba9bb46dc3c46d
|
|
BLAKE2b-256 checksum How to use checksums |
d3a24ce52e5cf229f6ac5e771057bfe3eccdb40baef4af52a1be00a57d506429
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 10, 2026.
Transparency log