feat: Add syntax support for destructuring, labels, and generators#52
Open
feat: Add syntax support for destructuring, labels, and generators#52
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
This branch expands SandboxJS support for several missing JavaScript language features and brings the runtime behavior closer to native JS.
next(value)flow,yieldexpression values, delegation behavior, and constructor shims in the eval contextWhy
SandboxJS was still missing a set of common language features that show up in ordinary application code. This branch closes those gaps so more real-world JavaScript can run inside the sandbox without workarounds.
Impact
Users can now evaluate a broader set of JavaScript patterns inside the sandbox, especially around function parameters, destructuring, labels, and generator control flow. The test suite also gets much better coverage around those semantics.
Validation
npm test -- --runInBandnpm run lint