It's working in development just because a local webserver is used in development, but no server exists when used in a local widget. Because of that, all the API requests must be handled manually. Would only need the ones related to authentication and live streaming, utilizing axios for those requests.
I still need to rework the privacy policy and terms of service for YouTube API quota increase anyway, so this isn't a priority until I finally get that quota increase, since that's very important for public scaling especially since YouTube doesn't use webhooks for their chat API, it's just polling the API over and over again, which is why the quota increase is necessary.
So using the official Google API JavaScript Client is not possible for slime2, due to this issue: https://github.com/google/google-api-javascript-client/issues/46
It's working in development just because a local webserver is used in development, but no server exists when used in a local widget. Because of that, all the API requests must be handled manually. Would only need the ones related to authentication and live streaming, utilizing
axios
for those requests.I still need to rework the privacy policy and terms of service for YouTube API quota increase anyway, so this isn't a priority until I finally get that quota increase, since that's very important for public scaling especially since YouTube doesn't use webhooks for their chat API, it's just polling the API over and over again, which is why the quota increase is necessary.