Skip to content

Moving Beyond eval() for Better Security? #74

Description

@mudcube

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.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions