Packages

@ai-sdk/fireworks

3.0.97 · 17 Nov 2026Apache-2.0936k / weekRepositoryHomepagenpmAtom feed

Your version

3.0.0

major25 Jun 2026Where it was published

3.0.97 is the newest release of 3.x.

In short

3 breaking5 new4 fixed3 internal

  • Breaking

    Remove CommonJS exports from all packages. All packages are now ESM-only ("type": "module"). Consumers using require() must switch to ESM import syntax.

  • Breaking

    Start v7 pre-release

  • Breaking

    Raise minimum supported Node.js version to 22. Supported versions: 22, 24, and 26.

Release note

Major Changes

  • Breaking

    Remove CommonJS exports from all packages. All packages are now ESM-only ("type": "module"). Consumers using require() must switch to ESM import syntax.

  • Breaking

    Start v7 pre-release

Patch Changes

  • Add AI Gateway hint to provider READMEs

  • Migrate providers to support new top-level reasoning parameter

  • Enable includeUsage for Fireworks so streaming responses report token usage

  • Add the promptCacheKey provider option for Fireworks prompt cache affinity
    and Kimi K2.6 model autocomplete, and remove the deprecated Kimi K2.5
    serverless model from autocomplete.

  • Trigger release for all packages after provenance setup

  • Only send provider credentials to same-origin response-supplied URLs

    Several provider clients followed a URL taken from the provider's API response (a polling/status URL or a final media URL such as polling_url, urls.get, result_url, result.sample, or video.uri) and reused the authenticated headers — or appended ?key=<API_KEY> — on that request. Because the host of the response-supplied URL was never validated, the long-lived API key was sent to whatever host the response named (a CDN in the benign case, or an attacker-chosen host if the provider response was tampered with), allowing credential exfiltration.

    A new isSameOrigin helper is added to @ai-sdk/provider-utils, and the affected fetches in @ai-sdk/black-forest-labs, @ai-sdk/fireworks, @ai-sdk/replicate, @ai-sdk/gladia, @ai-sdk/fal, and @ai-sdk/google now attach credentials only when the followed URL is same-origin with the provider's configured API origin. Requests to a foreign origin are made without the credential.

  • Breaking

    Raise minimum supported Node.js version to 22. Supported versions: 22, 24, and 26.

  • Trigger initial canary release

  • Trigger initial beta release

  • Add workflow serialization support to all provider models.

    @ai-sdk/provider-utils: New serializeModel() helper that extracts only serializable properties from a model instance, filtering out functions and objects containing functions. Third-party provider authors can use this to add workflow support to their own models.

    All providers: headers is now optional in provider config types. This is non-breaking — existing code that passes headers continues to work. Custom provider implementations that construct model configs manually can now omit headers, which is useful when models are deserialized from a workflow step boundary where auth is provided separately.

    All provider model classes now include WORKFLOW_SERIALIZE and WORKFLOW_DESERIALIZE static methods, enabling them to cross workflow step boundaries without serialization errors.

A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.