Install jupyterlab with Homebrew, apk, apt, dnf, pacman, winget, Nix, zypper

Project links

• Homepage
• Repository
• Package manager page

Commands and aliases

• jlpm
• jupyter
• jupyter-console
• jupyter-dejavu
• jupyter-events
• jupyter-execute
• jupyter-kernel
• jupyter-kernelspec
• jupyter-lab
• jupyter-labextension
• jupyter-labhub
• jupyter-migrate
• jupyter-nbconvert
• jupyter-run
• jupyter-server
• jupyter-troubleshoot
• jupyter-trust

Project history

Project Jupyter split from IPython in 2014 to make the notebook architecture language-agnostic, while IPython continued as the Python shell and kernel. JupyterLab began as the next-generation interface for that architecture: a browser IDE that kept the notebook document model but added a file browser, text editor, terminals, drag-and-drop work areas, and a TypeScript extension system.

The JupyterLab repository was created on GitHub on 2016-06-03. Project Jupyter announced the beta series on 2018-02-20, saying the 0.32 line was suitable for daily use and that the 1.0 line would stabilize the extension API. The JupyterLab documentation records the 1.0 release in June 2019 as the point where the project was ready for both end users and extension authors.

JupyterLab 4.0 was announced on 2023-06-06. That release mattered because Jupyter Notebook 7 reused JupyterLab components, making JupyterLab not just an alternative front end but a shared foundation for the modern Notebook application as well.

Adoption history

JupyterLab inherited the large Jupyter notebook user base in research, education, and data science, then broadened the interface to workflows that mix notebooks with terminals, scripts, markdown, CSVs, and extension-provided viewers. The input package metadata shows distribution through Homebrew, Debian, Fedora, Arch, Alpine, Nix, Ubuntu, winget, and openSUSE-family packages.

Its adoption is also tied to the extension ecosystem. Because JupyterLab exposes a plugin model and typed front-end APIs, tools such as Jupyter AI, debugger support, language-server integration, visualization viewers, and institutional JupyterHub deployments can use the same browser workspace rather than inventing separate notebook shells.

How it is used

JupyterLab is commonly launched with `jupyter lab` and used as a local or remote browser workspace for notebooks, consoles, terminals, text files, and data files. It is especially common where exploratory programming, visualization, reproducible analysis, and teaching need to live in the same interface.

Package users care about its server-side and front-end split: a Homebrew installation exposes many `jupyter-*` entry points, while Python packages and extensions supply kernels, server extensions, lab extensions, and file renderers around the core application.

Why package nerds care

JupyterLab is a package-manager heavyweight because it packages a full browser application, Python server pieces, JavaScript assets, kernels, and extension hooks behind a single command-line formula. It is the sort of package that reveals how much modern scientific computing depends on language runtimes and web tooling coexisting cleanly.

It is also historically important as the point where the notebook stopped being only a single document UI and became a workspace. For package nerds, that makes it a dependency magnet, a compatibility test for Python and Node-era build systems, and a visible marker of the Jupyter ecosystem's move from classic notebooks to componentized applications.

Timeline

• 2014: Project Jupyter is created from the language-agnostic parts of IPython.
• 2016-06-03: The JupyterLab GitHub repository is created.
• 2018-02-20: Project Jupyter announces the JupyterLab beta series as ready for daily use.
• 2019-06: JupyterLab 1.0 is released, with the extension API ready for extension authors.
• 2023-06-06: JupyterLab 4.0 is announced.
• 2024-02-26: JupyterLab 4.1 and Notebook 7.1 are announced together, reflecting Notebook 7's reuse of JupyterLab components.

Related projects

• Project Jupyter is the umbrella project for JupyterLab, Notebook, kernels, JupyterHub, and shared standards.
• IPython is the origin project whose notebook and language-agnostic components led to Jupyter.
• Jupyter Notebook is the classic notebook application and, in Notebook 7, reuses JupyterLab components.
• JupyterHub deploys JupyterLab and Notebook environments for multiple users.

Sources

• https://api.github.com/repos/jupyterlab/jupyterlab
• https://blog.jupyter.org/jupyterlab-4-0-is-here-388d05e03442
• https://blog.jupyter.org/jupyterlab-4-1-and-notebook-7-1-are-here-20bfc3c10217
• https://blog.jupyter.org/jupyterlab-is-ready-for-users-5a6f039b8906
• https://github.com/jupyterlab/jupyterlab
• https://jupyter.org/
• https://jupyterlab.readthedocs.io/en/3.6.x/getting_started/overview.html