Fixed SyntaxError when obfuscating a class that extends a boolean literal - #1420
Merged
sanex3339 merged 1 commit intoJul 9, 2026
Conversation
sanex3339
merged commit Jul 9, 2026
fecc145
into
javascript-obfuscator:master
13 of 15 checks passed
Member
|
Released in 5.4.4 |
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
2 participants
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.
class C extends true {}is valid JavaScript, butBooleanLiteralTransformerrewrotetrue/falseinto!![]/![]even in theextendsposition, emittingclass C extends ![] {}. A class heritage must be aLeftHandSideExpression, so that causes an earlySyntaxError. I skip the transformation when the literal is the classsuperClassand leave it unchanged; booleans everywhere else are still transformed as before. Added a regression test (it fails without the fix and passes with it).Fixes #1131