Skip to content

add option mangle.properties.undeclared: boolean #424

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

Merged
merged 1 commit into from
Aug 17, 2019
Merged

add option mangle.properties.undeclared: boolean #424

merged 1 commit into from
Aug 17, 2019

Conversation

gdh1995
Copy link
Contributor

@gdh1995 gdh1995 commented Aug 15, 2019

This will fix #397 by adding a option of mangle.properties.undeclared = true, which is false by default to keep backwards compatible.

@fabiosantoscode
Copy link
Collaborator

Quite a fringe use case, but I think this should go in. Thanks!

@fabiosantoscode fabiosantoscode merged commit 5d5c109 into terser:master Aug 17, 2019
@gdh1995
Copy link
Contributor Author

gdh1995 commented Aug 19, 2019

May I ask when will be a next release date of terser?

@gdh1995 gdh1995 deleted the may-mangle-undeclared branch August 19, 2019 03:14
@fabiosantoscode
Copy link
Collaborator

I want to release today after I fix #407 or if I can't fix it today I'll release it without a #407 fix.

@fabiosantoscode
Copy link
Collaborator

4.2.0 is out

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.

properties are not mangled if it's in a deferred top level object
2 participants