but that is also sort of caused by closure not rewriting correctly

KK cool yeah what I wished for a while is actually a "completely" custom optimization step that would not require GCC, but I know that this is never going to happen in my life span 😃

I'm gonna say that there is never going to be something that would be able to optimize everything found on npm

any optimizer is gonna make some compromises somewhere

closure is pretty darn good already. I only blame the bad JS on npm 😉

It wouldn't be too hard to declare some externs if everything didn't depend on everything else on npm. 😑

@mseddon in my particular case is not an externs issue, the problem manifests when require-ing npm modules...in general I agree with you though 😉