Yes
Heres a simple Hello World
index.html
<html>
<head>
<script src="https://extension-files.twitch.tv/helper/v1/twitch-ext.min.js"></script>
<script src="script.js"></script>
</head>
<body>
Hello
</body>
</html>
script.js
window.Twitch.ext.onAuthorized((auth) => {
console.log('got auth');
});
Thats it a working example that displays “Hello”. That is the bare minimum for an extension.
An extension that is just plain JS (well node for the EBS to do the calls)
An extension that is also just plain JS that I use to debug/test various Extension functions
Which is deployed to GitHub pages (a good CDN comparison to Twitch’s CDN as it’s static + in a sub folder)
Sounds like you are trying to use inline JS and it’s tripping based on the CSP rules.
All JS must be in JS files and none of it inline.
All my extensions are basic JavaScript, no frameworks no react.
The react boilerplate examples are just react boilerplate examples. They demonstrate one method of constructing a Twitch Extension.
You don’t have to use React and it sounds like most of your issues are due to not being super familiar with React and it’s build processes in “not normal react applications”
Running Node and React and other things like this are all optional and just one way to build an extension.
You could make it as static as possible (no JS Rendering from React for example) and run a regular Apache/Nginx server to run your test server off of, of even a php -S.
At the end of the day, a Twitch Extension is literally just a website, served from a sub folder, on a static CDN, so theres no Server Side Rendering, and no navigating. With one basic rule, include the JS Helper and a call to onAuthorized.
So build the extension however you want! It’s literally just a website