"unsafe-eval" in Chrome extension

Why does the extension use the ‘unsafe-eval’ function in manifest.json? These functions are notorious XSS attack vectors and could alarm users

Forgot the exact reason but for us it’s safe. The best to find out why is to build the extension without the parameter and see what happens.