Devframe

DF0063: Remote Asset Cache Write Failed

Failed to persist a remote asset into the cache at "{filepath}": {reason}

Message

Failed to persist a remote asset into the cache at "{filepath}": {reason}

Cause

A remote asset streamed through the CDN back-proxy to the browser, but writing the teed copy into the local cache directory (<project storage>/.remote-assets/<package>@<version>/…) failed, usually from a permissions problem, a full disk, or a removed node_modules. The response was still served; only caching failed, so the file streams through the provider again next request.

Fix

Check that the project storage directory (conventionally node_modules/.<app>/devframe/) is writable and has free space.

Source

DF0062: Installed Assets Package Version Skew

The locally installed "{package}@{installed}" differs from the required "{required}"; serving the installed one.

DF0064: Remote Assets Materialization Failed

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