-
Notifications
You must be signed in to change notification settings - Fork 27
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
Overhaul export support to allow for manual mangling of reserved words #105
Conversation
…nstead of application during discovery
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Update the README
with information about this new configuration.
@prateekbh – this is ready for review now. |
will review this today |
|
||
/** | ||
* When outputting ES2017+ code there is neglagible differences between `const` and `let` for runtime performance. | ||
* So, we replace all usages of `const` with `let` to enable more variable folding. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this really safe to do so?
Ready for review. This CL is large, and refactors how imports and exports are parsed and recovered.
The motivation is to add support for a new second argument to the plugin creation from Rollup.
With
mangleReservedWords
, a user of the plugin can specify reserved words that the Plugin should ensure are properly renamed before Closure Compiler is invoked. This addresses #92.Note: There are a lot of pitfalls for these kinds of changes to preserve the words (especially when a reserved word was used as an
import
orexport
).