jupyter-packaging
Jupyter Packaging Utilities.
Decision gist · record as of 2026-08-14
Yes, if you are packaging a Jupyter project with JavaScript or other pre-build requirements. Install as a build-only dependency in pyproject.toml, not as a runtime requirement. The package is actively maintained, has no known vulnerabilities, and is widely used in the Jupyter ecosystem. Do not add it to your package's runtime dependencies.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Intended for use during package build/development only; should not be listed as a runtime dependency in your package's requirements.
- Low install friction with a pure-Python wheel distribution.
- Actively maintained with recent commits; intended as a build-time dependency only, not a runtime requirement for end users.
License · maintenance · safety
permissive license (permissive) — BSD 3-Clause License permits commercial and private use with minimal restrictions; you may redistribute and modify freely provided you retain the license notice and disclaimer.
last release 2022-08-25 (1450 days) · last repo commit 2026-08-03 · 65 stars
0 known vulnerabilities (OSV.dev, 2026-08-14) · 989,138 downloads/mo, #4,567 on PyPI
Alternatives
Verify before relying
# In pyproject.toml
[build-system]
requires = ["jupyter_packaging>=0.10,<2"]
build-backend = "setuptools.build_meta"
# In setup.py
from jupyter_packaging import wrap_installers, npm_builder
builder = npm_builder()
cmdclass = wrap_installers(pre_develop=builder, pre_dist=builder)
from setuptools import setup
setup(cmdclass=cmdclass)- Whether the package supports Python 3.11+ despite classifiers listing only up to 3.10.
- Current status of the npm_builder for non-Node.js JavaScript toolchains or alternative build systems.
- Whether the package works with modern build frontends beyond setuptools.
What it is and what it does
Jupyter Packaging provides build-time utilities for Python packages that combine Python code with JavaScript assets or other pre-build steps. It wraps setuptools to inject custom build commands (like npm builds) before package distribution or development installation. The package is designed to be used as a build requirement in pyproject.toml, not as a runtime dependency—it helps package authors handle the complexity of building hybrid Python/JavaScript projects without burdening end users.
The package offers three integration patterns: as a build requirement with custom setup.py commands, as a full build backend via jupyter_packaging.build_api, or as a vendored setupbase.py module. It handles common Jupyter packaging tasks like managing pre-build steps, ensuring generated assets are included in distributions, and supporting both wheel and sdist formats through modern build tools.
Use it for
- Build a Jupyter extension that includes TypeScript/JavaScript components compiled during package installation.
- Manage npm build steps in a Python package without requiring end users to have Node.js installed.
- Ensure generated assets (CSS, bundled JS) are correctly included in wheel distributions and source tarballs.
- Develop a Jupyter lab plugin with a Python backend and npm-managed frontend build pipeline.
- Configure data files and assets for Jupyter packages using setuptools with pre-build hooks.
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes, if you are packaging a Jupyter project with JavaScript or other pre-build requirements.
Install as a build-only dependency in pyproject.toml, not as a runtime requirement. The package is actively maintained, has no known vulnerabilities, and is widely used in the Jupyter ecosystem. Do not add it to your package's runtime dependencies.
Install
jupyter-packaging on PyPI
Before you install
Low install friction with a pure-Python wheel distribution. Actively maintained with recent commits; intended as a build-time dependency only, not a runtime requirement for end users.
Intended for use during package build/development only; should not be listed as a runtime dependency in your package's requirements.
License in practice
BSD 3-Clause License permits commercial and private use with minimal restrictions; you may redistribute and modify freely provided you retain the license notice and disclaimer.
Quickstart
# In pyproject.toml
[build-system]
requires = ["jupyter_packaging>=0.10,<2"]
build-backend = "setuptools.build_meta"
# In setup.py
from jupyter_packaging import wrap_installers, npm_builder
builder = npm_builder()
cmdclass = wrap_installers(pre_develop=builder, pre_dist=builder)
from setuptools import setup
setup(cmdclass=cmdclass)Verify before relying
- Whether the package supports Python 3.11+ despite classifiers listing only up to 3.10.
- Current status of the npm_builder for non-Node.js JavaScript toolchains or alternative build systems.
- Whether the package works with modern build frontends beyond setuptools.
Package facts
| License | permissive license permissive |
| Python support | Supports the current Python release >=3.7 |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | 5 packagesdeprecationpackagingsetuptoolstomlkitwheel |
| Maintenance | Actively maintained 1,450 days since the last release |
| Last repo commit | |
| First released | |
| Downloads | 989,138 / month, #4,567 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
| Classifiers | Intended Audience :: DevelopersIntended Audience :: Science/ResearchIntended Audience :: System AdministratorsLicense :: OSI Approved :: BSD LicenseProgramming Language :: PythonProgramming Language :: Python :: 3.10Programming Language :: Python :: 3.7Programming Language :: Python :: 3.8Programming Language :: Python :: 3.9 |
Evidence: jupyter_packaging-0.12.3-py3-none-any.whl
Tags
Let your AI agent find packages like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 14,416 PyPI packages by what they can do, searchable in plain language.
wish › “jupyter package build tools”
- jupyter-packagingProvides build tools and utilities for packaging Jupyter Python…
- jupyter-builderProvides CLI and Python tools to build, develop, and watch JupyterLab…
- jupyterlite-coreProvides the core build and CLI infrastructure for JupyterLite, a…
Give your agent the search over MCP, or paste the wish link into any chat.
More Build Tools packages
Provides reusable utilities for Python packaging interoperability, including version handling, specifiers, markers, requirements, tags, and metadata parsing according to standards like PEP 440 and PEP 425.
Wraps any iterable to display a real-time progress bar in the terminal or Jupyter notebook, showing iteration count, elapsed time, and estimated time remaining.
pip is the standard installer for Python packages, enabling you to download and install packages from the Python Package Index and other indexes into your Python environment.
Hatchling is a standards-compliant Python build backend that handles packaging, metadata, and distribution of Python projects when configured in a project's pyproject.toml file.
Generates Python gRPC service stubs and message classes from Protocol Buffer definitions, enabling developers to build gRPC clients and servers.
pre-commit is a framework for installing and running git hooks written in any language before commits are made, automating code quality and validation checks across multi-language projects.
Install it if your team needs consistent, automated validation at commit time.
See also hatch-jupyter-builder · pyroma · flit-core · jupyter-builder · flit · setuptools · charmcraftlocal · setuptools-git · setuptools-scm