Which are my options to make it work?
This is hard to say without knowing why you’re using eval in your code or where it’s coming from. There’s a few possibilites:
- Your build pipeline wraps
evalaround the code. That should be easy to fix. - AlpineJS uses
evalinternally. You’ll have to find a way around that, either by configuring the library differently, if such an option exists, or by using a different library - You’re using
evalin your code to execute user search input (maybe something homegrown likemyValues.filter(x => eval("x." + userInput.replace(/=/, "=="))). You won’t be able to use this at all, and will need to come up with a different filtering strategy, such as manually parsing the input and looking at the various fields.
There is no way to publish a Twitch extension containing eval at all, you will need to either remove it or write code to replace it. eval is dangerous because your API could theoretically inject code to be executed after the extension has been released, and then it bypass approval. So by replacing it with manual filters or something the Twitch team can be sure that anything from the API cannot be actually run as code, only used as a string for comparison or similar.