API reference

Every public class, method, and event in @codexo/exojs. Generated from source.

I

interfaceAssetStats

@codexo/exojs / assets / stable

Aggregate view of what a loader currently holds, for HUDs and memory dashboards that want counters rather than the per-asset rows Loader.inspect returns. Counts follow the same five lifecycle states AssetInspection reports, collapsed to ready / pending / failed.

6
props
0
methods
0
events
Import
import { AssetStats } from '@codexo/exojs'

Aggregate view of what a loader currently holds, for HUDs and memory dashboards that want counters rather than the per-asset rows Loader.inspect returns.

Counts follow the same five lifecycle states AssetInspection reports, collapsed to ready / pending / failed.

Properties6
bytes: number
Estimated resident bytes over every ready asset. The loader cannot see inside a type's resource, so payloads are sized by shape: binary buffers and blobs by their length, strings by their UTF-16 length, decoded audio by its PCM footprint, and anything carrying pixel dimensions at four bytes per texel. A structured payload (parsed JSON, an XML document, a font face) contributes nothing, and GPU-side copies are not counted at all - read RenderStats.gpuMemoryBytes for those. Treat this as a floor on CPU-side asset memory, not an accounting of it.
Per type, largest resident footprint first, ties broken by type id.
failed: number
Assets whose last fetch attempt errored.
The heaviest resident assets, largest first, as many as were asked for.
pending: number
Assets that are claimed but not settled - idle, queued in the background lane, or fetching.
ready: number
Assets whose payload is resident and readable.
Source