CSP considerations: For best results, allow unsafe-eval in your Content Security Policy. Without it, a less effective fallback is used automatically. The browser-no-eval target uses the fallback by default.

Browser extensions: If your code runs in a browser extension with a restrictive CSP, use the browser-no-eval target for best compatibility.