CORS Request Block - Same Origin Policy

[BarryCarlyon]

@KJ_Keys

Though I am still pretty confused as I am still learning; If I follow along with “Twitch Extensions Part 6 – Dev Environment Updates – Content Security Policy!” and modify my code to consider CSP headers then it will permit communication between the front end and back end?

That depends as the error you have stated appears to be an error in the frontend server.

But if you are following the 101 Guide then the error shouldn’t be present.

But it’s a very outdated guide.

@KJ_Keys

Also, are any plans to update the Extension 101 tutorial series to reflect these changes?

At the end of the day, an extensions is LITERALLY just a website where the backend and frontend are no different servers, and theres no server side rendering on the frontend.

With one rule of “include and invoke the Twitch JS helper”

So if you can build a website then you can build an extension.

The tutorial goes thru some extra bits such has how to verify a message sent via AJAX from the frontend is from an extension or not. Which you could also totally skip.

So, if this doesn’t make sense, skip it and just start building your extension based on the knowledge that it is JUST a website at the end of the day.

As to if it will get update I don’t know, most of the examples and tutorials in the docs/TwitchDev github are super out of date both just in general changes to extensions but the old Twitch API being removed.