v0.3.1

Patch Changes

• f3095e5 Thanks @jwahdatehagh! - Expose sourceAnimationUri on token metadata responses when the API provides
  it.

v0.3.0

Minor Changes

• 271cba9 Thanks @jwahdatehagh! - Add api.token.fetchMetadata() for single-shot metadata requests. It
  makes exactly one HTTP call and returns a discriminated
  TokenMetadataResponse ({ status: 'ready' | 'pending', data }) — never
  throws on a pending response, and never polls. Useful when the caller
  wants to drive its own polling cadence (e.g. a frontend that polls a
  proxy endpoint and renders the partial data.name / sourceImageUri
  while waiting for the image cache).

  metadata() is now a thin polling wrapper around fetchMetadata and is
  fully backward-compatible.

  New public types: TokenMetadataResponse, TokenMetadataFetchOptions,
  TokenApi.

v0.2.0

Minor Changes

• 6e3935c Thanks @jwahdatehagh! - Handle the async-queue metadata response. The token metadata endpoint now returns a { status: 'ready' | 'pending' | 'error', data } envelope and can defer image caching to a background job. api.token.metadata() now polls until the image is ready (default: every 2.5s, up to 60s) and resolves with the fully cached metadata. New options: pollIntervalMs, maxWaitMs, signal, and onPending (fires with partial data on each pending response). New EvmNowMetadataPendingError is thrown when polling exhausts maxWaitMs, with the last partial TokenMetadata on .lastData. Server status: 'error' responses throw EvmNowApiError with the server's error message. The legacy { data: T } envelope auto-unwrap has been removed.

v0.1.2

Patch Changes

• a54c54b Thanks @jwahdatehagh! - Reshape token metadata response. Renames api.token.image() to api.token.metadata(), exposes the original tokenUri and sourceImageUri from the on-chain metadata, and simplifies the image field to { xs?, sm?, md?, lg? } with ready-to-use CDN URLs (the key and sizes wire fields are no longer surfaced).

v0.1.1

Patch Changes

• 4b4813f Thanks @yougogirldoteth! - Expand compact token image responses into CDN URLs for each available size. Token images now use the API response shape { key, sizes }.