You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently emscripten depends pretty strongly on closure compiler to get its absolute smallest output.
Over the years this is caused a lot of issue for us. For example:
Bugs in closure compiler itself.
Difficulty running closure compiler: Closure compile is available in 3 forms: JavaScript, Java, and native-compiled-gradle. All 3 of these have presented issues for us
Opaque limitations of closure. For example, I recently discoverted that it minifies things differently inside a nest scope that it does at the top level. This basically blocked my recent change: Move modularization code into js compiler #23261
Impossible to suppress warnings
Jumping through crazy hoops to avoid minification:
Finally, the future of closure compiler seems somewhat tenous and the npm packages have not been updated in 10 months.
We have a pretty annoying issue that there is not macOS arm64 binary still in npm: google/closure-compiler-npm#291. This means almost all mac users see warning messages and fall back to java version.
Can we remove our dependency on closure somehow?
The text was updated successfully, but these errors were encountered:
sbc100
changed the title
What should we do about our closure compiler dependency
What should we do about our closure compiler dependency?
Jan 9, 2025
Currently emscripten depends pretty strongly on closure compiler to get its absolute smallest output.
Over the years this is caused a lot of issue for us. For example:
emscripten/src/shell.js
Lines 28 to 29 in 0585506
emscripten/src/parseTools.mjs
Lines 47 to 54 in 675698d
Finally, the future of closure compiler seems somewhat tenous and the npm packages have not been updated in 10 months.
We have a pretty annoying issue that there is not macOS arm64 binary still in npm: google/closure-compiler-npm#291. This means almost all mac users see warning messages and fall back to java version.
Can we remove our dependency on closure somehow?
The text was updated successfully, but these errors were encountered: