@ai-sdk/fireworks
3.0.97 · 17 Nov 2026Apache-2.0936k / weekRepositoryHomepagenpmAtom feed
Upgrading @ai-sdk/fireworks From 1.0.13 to 1.0.67
51 releases in betweenevery note read
Reading releases, release notes and advisories…
Release by release
1.0.63 – 1.0.675 releases, nothing new or fixed in the notes
- Fixed
Keep default Node.js downloads protected by DNS validation and connection pinning when frameworks or instrumentation wrap global fetch before or after the SDK loads.
- Fixed
1.0.52 – 1.0.618 releases, nothing new or fixed in the notes
- Fixed
Parse the object error envelope Fireworks actually returns (
{"error":{"object","type","code","message"}}) instead of a bare string. The mismatched schema failed to parse, so error messages silently degraded to the HTTP reason phrase —Bad Requestover HTTP/1.1, and an empty string over HTTP/2, which has no reason phrase. Fireworks' own message now reaches the caller, e.g.Model not found, inaccessible, and/or not deployedrather thanNot Found.
- Fixed
- Fixed
Send
promptCacheKey,serviceTier,reasoningHistoryandthinking.budgetTokensunder the snake_case names the Fireworks API defines. Fireworks rejects unknown fields outright, so previously any of these provider options failed the whole request with400 Extra inputs are not permitted.
- Fixed
1.0.43 – 1.0.497 releases, nothing new or fixed in the notes
- New
Enable
includeUsagefor Fireworks so streaming responses report token usage
- New
- Fixed
Only send provider credentials to same-origin response-supplied URLs
- Fixed
51 internal lines (docs, tests, tooling) left out.
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.