{"categories":[{"label":"Build Tools","url":"https://skillfed.io/packages/category/software-development-build-tools/3"}],"enrichment":{"capability":"Provides Hatch plugins to read and write Python package version and metadata from a Node.js package.json file, enabling version-source and metadata-hook integration.","skillfed_tags":["hatch-plugin","version-management","nodejs-integration"],"use_cases":["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."],"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.\n\nThe 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.","worth_installing":"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\u2014the package is stable and the repository remains active\u2014but verify that your version format and metadata fields align with the plugin's supported subset before adopting it."},"id":"hatch-nodejs-version","links":{"html":"https://skillfed.io/packages/hatch-nodejs-version","md":"https://skillfed.io/packages/hatch-nodejs-version.md","pypi":"https://pypi.org/project/hatch-nodejs-version/"},"maintenance":{"status":"aging"},"meta":{"latest_release":"2025-07-24","license_spdx":null,"license_treatment":"permissive","name":"hatch-nodejs-version","python_support":"supports_current","summary":"Hatch plugin for versioning from a package.json file"},"popularity":{"monthly_downloads":204900,"position":9598,"tier":"top_15000"},"security":{"n_vulnerabilities":0},"version":"0.4.0"}
