hatch-nodejs-version
Hatch plugin for versioning from a package.json file
Decision gist · record as of 2026-08-14
Yes, if you maintain both Python and Node.js distributions or want to keep version and metadata in package.json as a single source of truth. The plugin has low install friction, permissive licensing, and no known vulnerabilities. The aging maintenance status (386 days since last release) is not a blocker—the package is stable and the repository remains active—but verify that your version format and metadata fields align with the plugin's supported subset before adopting it.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Requires a package.json file in the project root (or at a configured path) with a version field; only accepts semver versions compatible with PEP 440 (major.minor.patch[-pre-release][-dev-release]).
- Low install friction with a single runtime dependency on hatchling.
- The package is aging (386 days since last release) but remains actively maintained with recent commits; supports current Python versions 3.9–3.13.
License · maintenance · safety
MIT (permissive) — MIT license is permissive and imposes no restrictions on use, modification, or distribution in proprietary or open-source projects.
last release 2025-07-24 (386 days) · last repo commit 2025-07-24 · 10 stars
0 known vulnerabilities (OSV.dev, 2026-08-14) · 204,900 downloads/mo, #9,598 on PyPI
Alternatives
Verify before relying
# Add to pyproject.toml
[build-system]
requires = ["hatchling", "hatch-nodejs-version"]
build-backend = "hatchling.build"
[tool.hatch.version]
source = "nodejs"
# Then hatch reads version from package.json automatically during build- Whether the metadata hook correctly handles all PEP 621 fields when reading from package.json, or only a subset.
- Performance impact of metadata hook on build time for large package.json files.
- Compatibility with monorepo setups where package.json may be in a non-standard location.
What it is and what it does
This is a Hatch build plugin that bridges Python and Node.js packaging by reading version and metadata from a package.json file instead of requiring them to be duplicated in pyproject.toml. It provides two plugins: a version-source plugin that treats package.json as the single source of truth for version numbers, and a metadata-hook plugin that populates Python package metadata (author, description, URLs) from corresponding fields in package.json.
The plugin is designed for projects that maintain both Python and Node.js distributions or that want to keep version information in a single place. It handles conversion between semantic versioning (used by Node.js) and PEP 440 (Python's versioning standard), accepting only the common subset: major, minor, patch, pre-release, and dev-release components. The version-source plugin supports round-trip consistency, meaning versions can be read from and written back to package.json without loss of information, provided delimiters are chosen carefully.
Use it for
- Maintain a single version number in package.json for a project that publishes both Python and Node.js packages.
- Automatically populate Python package metadata (author, repository, homepage) from an existing package.json without manual duplication.
- Ensure version consistency across Python and Node.js distributions during CI/CD builds.
- Migrate a Node.js project to Python packaging while keeping version management in the familiar package.json format.
- Use package.json as the canonical metadata source for monorepo or polyglot projects.
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes, if you maintain both Python and Node.js distributions or want to keep version and metadata in package.json as a single source of truth.
The plugin has low install friction, permissive licensing, and no known vulnerabilities. The aging maintenance status (386 days since last release) is not a blocker—the package is stable and the repository remains active—but verify that your version format and metadata fields align with the plugin's supported subset before adopting it.
Install
hatch-nodejs-version on PyPI
Before you install
Low install friction with a single runtime dependency on hatchling. The package is aging (386 days since last release) but remains actively maintained with recent commits; supports current Python versions 3.9–3.13.
Requires a package.json file in the project root (or at a configured path) with a version field; only accepts semver versions compatible with PEP 440 (major.minor.patch[-pre-release][-dev-release]).
License in practice
MIT license is permissive and imposes no restrictions on use, modification, or distribution in proprietary or open-source projects.
Quickstart
# Add to pyproject.toml
[build-system]
requires = ["hatchling", "hatch-nodejs-version"]
build-backend = "hatchling.build"
[tool.hatch.version]
source = "nodejs"
# Then hatch reads version from package.json automatically during buildVerify before relying
- Whether the metadata hook correctly handles all PEP 621 fields when reading from package.json, or only a subset.
- Performance impact of metadata hook on build time for large package.json files.
- Compatibility with monorepo setups where package.json may be in a non-standard location.
Package facts
| License | MIT permissive |
| Python support | Supports the current Python release >=3.9 |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | 1 packagehatchling |
| Maintenance | Aging 386 days since the last release |
| Last repo commit | |
| First released | |
| Downloads | 204,900 / month, #9,598 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
| Classifiers | Framework :: HatchProgramming Language :: Python :: 3.10Programming Language :: Python :: 3.11Programming Language :: Python :: 3.12Programming Language :: Python :: 3.13Programming Language :: Python :: 3.9 |
Evidence: hatch_nodejs_version-0.4.0-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 › “hatch version from package.json”
- hatch-nodejs-versionProvides Hatch plugins to read and write Python package version and…
- hatch-vcsA Hatch plugin that automatically determines your project's version…
- uv-dynamic-versioningA Hatch plugin that automatically derives package versions from VCS…
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-vcs · hatch-requirements-txt · hatch-regex-commit · hatch-fancy-pypi-readme · hatchling-autoextras-hook · versioningit · hatch-jupyter-builder · hatch · httptools