chore: fix handling of error logging in API request

[0xlora]

Why is this change needed?

I've fixed the issue where the response variable might not be available in the catch block. Instead of trying to log the response when an error occurs, we now log the actual error (e).
This ensures better error tracking even when the request fails.

Merge Checklist

• PR title adheres to the conventional commits standard
• PR has a changeset
• PR has been tagged with a change label(s) (i.e. documentation, feature, bugfix, or chore)
• PR includes documentation if necessary.

---

PR-Codex overview

This PR focuses on improving error handling in the code by changing the logged output when an error occurs.

Detailed summary

• In the catch block, the logged output was changed from console.log(response); to console.log(e);, ensuring that the actual error e is logged instead of the response.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

[changeset-bot]

⚠️ No Changeset found

Latest commit: 2a972d5

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
hub-monorepo	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 11, 2025 6:36pm