chore: improve getResponseData

[Uzlopak]

first #711 should be merged, than I want to see if there is some aspects regarding resilience.

[github-actions]

👋 Hi! Thank you for this contribution! Just to let you know, our GitHub SDK team does a round of issue and PR reviews twice a week, every Monday and Friday! We have a process in place for prioritizing and responding to your input. Because you are a part of this community please feel free to comment, add to, or pick up any issues/PRs that are labeled with Status: Up for grabs. You & others like you are the reason all of this works! So thank you & happy coding! 🚀

[Uzlopak]

@gr2m
@wolfy1339
Do we need to support browsers? In Nodejs we have MIMEType class, and we can use it as a reliable content type parser. But if we need browser support we could e.g. use fast-content-type-parser (made by me and used in fastify).

[wolfy1339]

The whole Octokit ecosystem (apart from some exceptions) has browser support.

[Uzlopak]

@wolfy1339

I introduced the package fast-content-type-parse. It is a package I wrote myself, as I mentioned before. It is imho more reliable than using regexes. We use it in fastify. Using safeParse to not throw errors if the content type is invalid. The chance is imho slim.

Also i think i made it more resilient, because it has no chance to throw anymore ;).

[github-actions]

🎉 This PR is included in version 9.1.4 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)

Your semantic-release bot 📦🚀