-
-
Notifications
You must be signed in to change notification settings - Fork 407
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
Custom configuration broken in 2.7.0-rc2 #122
Comments
Yea, at this point it's better switching to something else, perhaps uglifyjs? I'd rather have a bit bigger filesize than a broken plugin. Just tested and Closure compiler with |
Agreed, also just for the record:
So the difference between SIMPLE and ADVANCED is quite minor, especially considering the gziped size. |
It's up, third time's a charm! Man, @tillsanders' gonna hate me for all these releases ... |
@orestbida As a matter of fact, I love how much effort you put into this project ❤️
… Am 26.11.2021 um 00:16 schrieb Orest Bida ***@***.***>:
It's up, third time's a charm! Man, @tillsanders' gonna hate me for all these releases ...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Hi, unfortunately the fix in #120 did not work as expected.
What happes in the Closure compiler now, is the keys in the
_config
defaults are preserved (thanks to #120), however, name of the actual value which is used is still minified. Meaning the_config
now contains... so in the end
getConfig()
returns value from the default configuration, not the actual used one.The way of fixing this obviously requires accessing the config as an array arguments, for example:
and doing so on all places. This should force the Closure compiler to avoid renaming of the fields. However, I'm not sure whether this solution is preferred, there still may be edgecases and unexpected bugs. There are two other options:
SIMPLE_OPTIMIZATIONS
level in Closure compiler.What do you think, @orestbida?
The text was updated successfully, but these errors were encountered: