It was a piece of code that supposed to be running with the extension, not on the browser. Though it’s fixed!

Thanks again!