Add argument to control whether NamespaceResolver attempts to pair mangled constructors #10
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.
I ran into a few issues with Resurrect-JS while messing with one of my scripts. Enabling variable mangle in uglify mangled constructor names and broke NamespaceResolver. I was going to make my own or manually wrap the internal resolver but I came up with this change to automatically resolve my objects even if I update them later. I think it could be a really useful feature.
I created a couple performance tests here. The (un-uglified) source object I used is below