Struct ResolvedPackage 

pub struct ResolvedPackage {

    pub dep_path: String,
    pub name: String,
    pub version: String,
    pub integrity: Option<String>,
    pub tarball_url: Option<String>,
    pub alias_of: Option<String>,
    pub local_source: Option<LocalSource>,
    pub os: PlatformList,
    pub cpu: PlatformList,
    pub libc: PlatformList,
    pub deprecated: Option<Arc<str>>,
    pub unpacked_size: Option<u64>,
    pub pending: usize,
}

A resolved package emitted during resolution, allowing the caller to start fetching tarballs before resolution is fully complete.

Fields

dep_path: String

name: String

version: String

integrity: Option<String>

tarball_url: Option<String>

Exact tarball URL reported by the packument’s dist.tarball field, or preserved from an existing lockfile. Most npm packages can re-derive this from name + version, but JSR’s npm-compatible registry uses opaque tarball paths, so fetchers must prefer this when it is available.

alias_of: Option<String>

Real registry name when this package is an npm-alias ("h3-v2": "npm:h3@..."). name is the alias (h3-v2 — the folder in node_modules/), alias_of is what the streaming fetch client uses to derive the tarball URL and store-index key. None for non-aliased packages, in which case name already matches the registry.

local_source: Option<LocalSource>

Set for non-registry packages (file: / link:). Downstream fetchers short-circuit the tarball path and materialize from disk instead.

os: PlatformList

npm os/cpu/libc arrays straight from the packument (or lockfile). The streaming fetch coordinator uses them to defer tarball downloads for optional natives that won’t install on the host — a post-resolve catch-up pass after filter_graph fetches anything that survived the graph trim but got deferred, so required-platform-mismatched packages (which filter_graph doesn’t drop) still get their tarball before link.

cpu: PlatformList

libc: PlatformList

deprecated: Option<Arc<str>>

Deprecation message from the registry, carried forward so the install command can render user-facing warnings without a second packument fetch. Only populated on the fresh-resolve path; lockfile-reuse and file:/link: packages carry None because the packument wasn’t consulted. allowedDeprecatedVersions suppression is applied upstream, so anything set here is meant to surface to the user.

unpacked_size: Option<u64>

Best-effort install-size hint from the packument’s dist.unpackedSize. Summed across the resolve stream to drive the 4.2 MB / ~13.8 MB segment in the progress bar. None when the packument doesn’t carry the field (older publishes, file:/link: deps, JSR packages without npm metadata).

pending: usize

Resolver’s view of remaining work at the moment this package was sent: the size of the BFS queue plus any packument fetches still in flight plus transitives deferred behind a time-based cutoff. received_count + pending is a non-strict lower bound on the final resolved-package count, used by the install progress UI to render a real bar during the resolving phase instead of an empty placeholder. Approximate by construction — a packument fetch completing without enqueueing children can transiently shrink the frontier, so the install side raises the displayed denominator with fetch_max semantics.

Implementations

impl ResolvedPackage

pub fn registry_name(&self) -> &str

Registry lookup name — alias_of when set, otherwise name. Every tarball URL + store index site routes through this accessor so aliased packages resolve to the real registry entry without leaking the alias-qualified name into network requests (where it would 404).

Trait Implementations

impl Clone for ResolvedPackage

fn clone(&self) -> ResolvedPackage

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for ResolvedPackage

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.