--- title: 'DF0059: Remote Assets File Listing Failed' description: 'Failed to fetch the file listing for "{package}@{version}" from {provider}: {reason}' --- ## Message > Failed to fetch the file listing for "`{package}`@`{version}`" from `{provider}`: `{reason}` ## Cause A remote-assets source resolves request paths against the CDN provider's file-listing API (`data.jsdelivr.com` for jsDelivr, `?meta` for unpkg, or a custom provider's `listFiles`). That listing request failed, usually because the provider is unreachable or returned an error status. ## Fix Requests fall back to probing each candidate path against the provider directly. To resolve it: - Check network access to the configured provider, or switch providers (`provider: 'unpkg'` or a custom mirror). - Install the assets package locally (`npm install `); a local copy is served with zero network and needs no listing. ## Source - [`packages/devframe/src/utils/remote-assets.ts`](https://github.com/devframes/devframe/blob/main/packages/devframe/src/utils/remote-assets.ts): `createRemoteAssetsStore()` reports this (once per store) when the provider's file listing cannot be fetched or parsed.