Accept an already-parsed body in HttpError.from() (1.2.0)

[freshlogic]

Summary

HttpError.from() gains an optional second argument — an already-parsed JSON body:

• from(response) — unchanged; reads the body via response.clone().
• from(response, json) — uses the body you already read instead of re-reading the response.

This fixes the common pattern where a 200 response carries an errors[] envelope: once you've read the body with await response.json(), the response stream is consumed, so a second from(response) can't read it (you get a bare "200 OK"). Passing the parsed body — from(response, json) — captures the detail, and the error still carries the response status and cause.

if (!response.ok) {
    throw await HttpError.from(response);
}
const json = await response.json();
if (json.errors?.length) {
    throw await HttpError.from(response, json);
}

Backward compatible — from(response) behavior is identical.

Also

• Reformatted CHANGELOG.md to Keep a Changelog, matching the other @stores.com packages.

Testing

node --test — 15 pass / 0 fail; eslint clean. New tests cover from(response, json) (uses the passed body without re-reading, JSON:API detail, status-message fallback).

🤖 Generated with Claude Code

[coveralls]

Coverage Report for CI Build 26485767779

Coverage decreased (-3.7%) to 96.341%

Details

• Coverage decreased (-3.7%) from the base build.
• Patch coverage: 2 uncovered changes across 1 file (26 of 28 lines covered, 92.86%).
• No coverage regressions found.

Uncovered Changes

File	Changed	Covered	%
index.js	28	26	92.86%

Coverage Regressions

No coverage regressions found.

---

Coverage Stats

Relevant Lines:	66
Covered Lines:	64
Line Coverage:	96.97%
Relevant Branches:	16
Covered Branches:	15
Branch Coverage:	93.75%
Branches in Coverage %:	Yes
Coverage Strength:	5.05 hits per line

---

💛 - Coveralls