DF0063: Remote Asset Cache Write Failed
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 a permissions problem, a full disk, or a removed node_modules.
The response itself was served; only caching failed, so the same file will stream through the provider again on the next request.
Fix
Check that the project storage directory (conventionally node_modules/.<app>/devframe/) is writable and has free space.
Source
packages/devframe/src/utils/remote-assets.ts—createRemoteAssetsStore()'s background cache write reports this when persisting a fetched file fails.