Package Name Guidelines" (npm Docs)¶
Package Name Guidelines" (npm Docs).
Cited by¶
1 citation across 1 artifact.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Appellation
- In software package ecosystems, a package name within a registry is an appellation: the entity is the package, the opaque token is the registered name, the registrar is the package index that guarantees uniqueness within its namespace, and the portable handle is what every dependency declaration routes through.
This sourceDocuments how a package name within the registry is an authoritative, namespace-unique identifier (uniqueness enforced at publish time; scopes for disambiguation), through which dependents refer to a package by name rather than contents — the indirection that lets maintainers ship new versions without invalidating downstream references.
- In software package ecosystems, a package name within a registry is an appellation: the entity is the package, the opaque token is the registered name, the registrar is the package index that guarantees uniqueness within its namespace, and the portable handle is what every dependency declaration routes through.
Verification¶
This reference passed the adversarial substantiation pipeline: it was checked to exist and to support the claim it is attached to. See how references were verified.
Registry ID ref:9aafbc23a8c4 · see in the full table