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

fix(runtime/js/timers): Use (0, eval) instead of eval() #10103

Merged
merged 1 commit into from
Apr 11, 2021

Conversation

nayeemrmn
Copy link
Collaborator

Fixes #10091.

runtime/js/11_timers.js Outdated Show resolved Hide resolved
@nayeemrmn nayeemrmn changed the title fix(runtime/js/timers): Use core.evalContext() instead of eval() fix(runtime/js/timers): Use (0, eval) instead of eval() Apr 10, 2021
Copy link
Contributor

@bnoordhuis bnoordhuis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. One suggestion: maybe add a regression test?

Copy link
Member

@bartlomieju bartlomieju left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@bartlomieju bartlomieju merged commit 8b49d94 into denoland:main Apr 11, 2021
@nayeemrmn nayeemrmn deleted the timers-eval branch April 11, 2021 23:41
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

Successfully merging this pull request may close these issues.

Use of eval in setTimeout/setInterval leaks internal scope
3 participants