RESOURCE

Implementation: supported · Proposal: in-review (status checked 2026-10-31). Resource fetching has focused shim and type tests; the reverted merge and reopened proposal do not change that implementation assessment. All capabilities remain subject to change. Maturity and opt-in policy.

Sandboxed byte fetching (info() -> ResourceInfo, bytes(url, options?) -> Blob, bytesMany(requests) -> ResourceBytesItem[]) over https / blossom (BUD-10 blossom:<sha256>.<ext> URIs) / nostr / data schemes — the only network-fetch primitive available inside the iframe sandbox.

const info = await window.napplet.resource.info();
const blob = await window.napplet.resource.bytes('blossom:<sha256>.png', {
  servers: ['https://cdn.hzrd149.com'],
});
const items = await window.napplet.resource.bytesMany([
  { url: 'https://example.com/avatar.png' },
  { url: 'blossom:<sha256>.png', servers: ['https://cdn.hzrd149.com'] },
]);

// Managed object URL — revoke when done to free memory
const { url, revoke } = window.napplet.resource.bytesAsObjectURL('blossom:<sha256>.png');
imgEl.src = url;
imgEl.onload = () => revoke();

This non-normative guide defers to the living NAP-RESOURCE proposal. Feature-gate with if (window.napplet?.resource) before use; the runtime injects only available domains. Typed helpers ship from @napplet/nap/resource and @napplet/sdk.

RESOURCE ​

RESOURCE