twitchdev / extension-getting-started Goto Github PK

I'm not sure if this is in the right place, as it seems to be more an issue to do with the native Developer Rig than anything, but the native Developer Rig doesn't seem to be on GitHub, so I'm posting this here. Let me know if there's a better place for it. I downloaded the native Developer Rig, and created a new project with this boilerplate. Upon running the frontend and backend, and creating a new video component extension view, I could not see the extension, I saw the below.

I then opened it in a browser, and upon investigation, found that the extension was rendering, but an element above it was collapsed to be 2px by 2px, so everything contained, including the extension wasn't visible.

I found to fix this I had to change some CSS manually on this element.

I had to change the CSS to the follow (the top and bottom are most likely resolution dependent I imagine, more a quick fix than anything just to get something visible and over the video portion of the player):

element.style {
    border: 1px solid rgb(125, 85, 199);
    left: 0px;
    position: absolute;
    top: 100px;
    /* height: 0px; */
    /* width: 0px; */
    bottom: 80px;
    right: 0;
}

Once I did this, the extension was visible as expected:

However this isn't possible to do so that it shows up in the Developer Rig.

Am I doing something wrong, is there any extra configuration that needs to be done? Or is this an issue with the Developer Rig? If it's an issue with the rig, do you know how to escalate it so it can be fixed?

Number 6 does not exist................

Twitch Developer Rig is not supported anymore, there are still a lot of references to this in this repos.
https://discuss.dev.twitch.tv/t/end-of-support-for-the-twitch-developer-rig/42995

AJAX request sent from front-end is permanently held by preflight requests,
causing the sample code unable the refresh with initial color nor cycle when clicking the button.

Possible fix:

1. Replace and update the hapi package to @hapi/hapi
2. Add a route in the backend for OPTIONS method to handle the preflight request.