Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Moving Beyond eval() for Better Security? #74

Open
mudcube opened this issue Aug 27, 2024 · 0 comments
Open

Moving Beyond eval() for Better Security? #74

mudcube opened this issue Aug 27, 2024 · 0 comments

Comments

@mudcube
Copy link
Contributor

mudcube commented Aug 27, 2024

Currently the distribution builds of Infinite Tree have multiple eval() calls. There are several contexts and situations where using eval() is either prohibited or strongly discouraged. For example; Chrome Extensions, Content Security Policy (CSP) environments, JavaScript strict mode and so forth.

This appears to be introduced in the WebPack build process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant