> Google has deprecated @expose so this solution may stop working some day.
I would take that deprecated bit with a grain of salt: https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/closure-compiler-discuss/pZaodHd0KD0/p767zHJzWO8J I read that thread to mean that they want to get rid of the side effects of @expose in one particular use case, and therefor introduced a new annotation. It remains the preferred way to prevent property renaming, it seems. No worries ;-) I'm keeping an eye on the compiler's new type inference and ES6 support progress, I'll keep you posted. EdB -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl