Skip to content
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

Consider Google Closure Compiler for production build #3

thesephist opened this issue May 15, 2019 · 0 comments


None yet
1 participant
Copy link

commented May 15, 2019

Closure Compiler is the gold standard of optimizing JS compilers, but when I took a look in May 2019 there were a few issues.

  • Some type inferences aren't working quite well
  • GCC includes $jscomp polyfills for modern JS features like Maps/Sets and WeakMaps which Torus uses extensively, and especially when Torus targets modern browsers this tends to bloat the bundle size quite a bit (frequently over 2x)

I've @suppress'd my way through (1) but (2) seemed like a deal breaker and I couldn't figure out how to remove those polyfills given my limited time with it. May come back to it down the line as I play with Closure Compiler more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.