---
title: "DF0064: Remote Assets Materialization Failed"
description: "Failed to materialize the remote assets of \"{package}@{version}\": {reason}"
canonical_url: "https://devfra.me/errors/df0064"
---
# DF0064: Remote Assets Materialization Failed

> Failed to materialize the remote assets of "\{package}@\{version}": \{reason}

## Message

> Failed to materialize the remote assets of "`{package}`@`{version}`": `{reason}`

## Cause

A static build (`createBuild`) with remote-assets `clientAssets` needs every asset file up front so the output is self-contained. Materialization walks the provider's file listing and downloads each file; one of those steps failed: the provider has no `listFiles`, the listing request failed, or a file download errored.

## Fix

- Install the assets package locally (`npm install <package>@<version>`); builds copy from the local install and touch no network.
- Otherwise ensure the provider and its file-listing API are reachable during the build, or configure a custom provider that implements `listFiles`.

## Source

- [`packages/devframe/src/utils/remote-assets.ts`](https://github.com/devframes/devframe/blob/main/packages/devframe/src/utils/remote-assets.ts): `createRemoteAssetsStore()`'s `materialize()` throws this when the file listing is unavailable or a download fails.


## Sitemap

See the full [sitemap](https://devfra.me/sitemap.md) for all pages.
