feat!: pass-through response status and headers to client

[mattmess1221]

Breaking Change

🔗 Linked issue

Resolves #25 and #41

❓ Type of change

• 📖 Documentation (updates to the documentation, readme or JSDoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

This change forwards the status code and headers from the API to the client. It also ensures any api errors are forwarded to the client as is.

Since ofetch always reads the body no matter what, it has to be read in as an ArrayBuffer then converted to an Uint8Array.

An additional side-effect of this is the decoded body is forwarded instead of raw, which means if a content-encoding response header is set, it will be wrong. Removing this header corrects that.

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[netlify]

✅ Deploy Preview for nuxt-api-party ready!

Name	Link
🔨 Latest commit	2c7f1c0
🔍 Latest deploy log	https://app.netlify.com/sites/nuxt-api-party/deploys/64f0e8e18c7a6c0008a9445e
😎 Deploy Preview	https://deploy-preview-44--nuxt-api-party.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[johannschopplich]

I love this approach. It should suit most use-cases and is worth a breaking change. Well done. 👏

[johannschopplich]

Have you tested $fetch.raw behaves the same in other environments, like Cloudflare? Will test it a bit myself as well.

[mattmess1221]

I don't see why it would behave differently. If anything, putting it behind cloudflare would either suppress or expose the issue if it re-compresses the response. Honestly, the only reason I noticed this was because jsonplaceholder comments had the header content-encoding: br