qcobjects: latest dist-tag is a pre-release (-beta)
Repo: https://github.com/QCObjects/QCObjects
Problem
The latest npm dist-tag for qcobjects points to 2.5.142-beta. Because this is a pre-release, npm's default resolver will not match it for ranges like ^2.4.95 or >=2.4.95 unless the consuming range also contains a pre-release tag.
This causes downstream packages to resolve to qcobjects@2.4.99 instead, creating peer dependency conflicts with qcobjects-cli (which requires qcobjects@^2.5.142-beta).
Fix
Publish a stable release from the v2.5-beta line (e.g., 2.5.142) and update the latest dist-tag:
npm dist-tag add qcobjects@2.5.142 latest
This will allow ^2.4.95 and ^2.5.142-beta ranges to converge on a single compatible version.
Impact
Prevents clean dependency resolution across the entire QCObjects ecosystem on npm >=10. Forces all downstream users to use --legacy-peer-deps.
qcobjects:
latestdist-tag is a pre-release (-beta)Repo: https://github.com/QCObjects/QCObjects
Problem
The
latestnpm dist-tag forqcobjectspoints to2.5.142-beta. Because this is a pre-release, npm's default resolver will not match it for ranges like^2.4.95or>=2.4.95unless the consuming range also contains a pre-release tag.This causes downstream packages to resolve to
qcobjects@2.4.99instead, creating peer dependency conflicts withqcobjects-cli(which requiresqcobjects@^2.5.142-beta).Fix
Publish a stable release from the
v2.5-betaline (e.g.,2.5.142) and update thelatestdist-tag:This will allow
^2.4.95and^2.5.142-betaranges to converge on a single compatible version.Impact
Prevents clean dependency resolution across the entire QCObjects ecosystem on npm >=10. Forces all downstream users to use
--legacy-peer-deps.