Deprecating and Undeprecating Packages or Package Versions¶
Deprecating and Undeprecating Packages or Package Versions.
Cited by¶
1 citation across 1 artifact.
Primes¶
- Alias-to-Authority Mapping
- In package registries, old names redirect to new ones after a rename or fork, so existing imports still resolve.
Supported in partVerified against the work's full text
npm deprecation leaves the old name installable and can point users to a replacement via a message, but it is not an automatic redirect and the page says nothing about forks.
“A deprecation warning or message can say anything. You may wish to include a message encouraging users to update to a specific version, or an alternate, supported package.”
- In package registries, old names redirect to new ones after a rename or fork, so existing imports still resolve.
Verification¶
Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.
Does it back the claim? Read against the text for 1 of 1 citation: 1 supported in part. Each verdict is shown under its citation below, with what in the work backs the sentence.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:53de1a45e021 · see in the full table