closure-compiler
minification-benchmarks
Our great sponsors
closure-compiler | minification-benchmarks | |
---|---|---|
14 | 15 | |
7,247 | 1,207 | |
0.6% | - | |
9.6 | 9.0 | |
8 days ago | 9 days ago | |
Java | TypeScript | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
closure-compiler
-
TypeScript Might Not Be Your God: Case Study of Migration from TS to JSDoc
The most well-known tools that rely on JSDoc are Closure Compiler (not to be confused with the Closure programming language) and TypeScript. Both of these tools can help make your JavaScript typed, but they approach it differently. Closure Compiler primarily focuses on enhancing your .js files by adding typing through JSDoc annotations (after all, they are just comments), while TypeScript is designed for .ts files, introducing its own well-known TypeScript constructs such as type, interface, enum, namespace, and so on.
-
Minify and Gzip (2022)
Closure Compiler follows the same line of thinking:
https://github.com/google/closure-compiler/wiki/FAQ#closure-...
- Svelte is migrating from TypeScript to JSDoc
-
Do any engines or optimizers product TS-specific performance gains?
I think only Google Closure Compiler did some optimizations based on its JSDoc-style annotations (see docs). If I remember correctly, types mostly allowed renaming objects' properties across modules, but most other advanced optimizations (like dead code elimination or functions inlining) didn't rely on types. In my experience properties renaming resulted in subtle, hard to discover bugs and I'd say they didn't bring much benefit.
- Can something like typescript or elm be AOT-compiled efficiently?
-
What does it mean?: *Template parameter* in Google style guide
The @template tag is supported by Google Closure Compiler
- Google announces a new OS written in Rust
-
Google Fonts Pull Requests Ignored
i'm not sure you want them to write back https://github.com/google/closure-compiler/pull/3958
time to fork
- Why don't we do this instead of TypeScript?
-
Is anyone using Google Closure Compiler? And why not?
I just came across the Google Closure Compiler. As the documentation says, it does not create machine code, but rather, "compiles JavaScript to better JavaScript".
minification-benchmarks
-
Extremely reducing the size of NPM package
Minifiers are used to reduce the size of the bundle. They can remove unused code, shorten expressions, and so on. And Now there are already several popular minifiers, and they continue to appear: more familiar ones - written in JavaScript - Terser and UglifyJS, even Babel has its own version of the minifier, there are also more modern SWC (written in Rust) and ESBuild (written in Go), and a bunch of other lesser-known minifiers. And I recommend you to look at this repository. It contains up-to-date test results of various popular minifiers.
-
Minify and Gzip (2022)
This minify/gzip size effect is a well known quirk to developers of javascript minifiers. The minifier's symbol mangling algorithm often has a more pronounced effect than does advanced AST optimization.
This website has real life data on the matter for popular libraries:
* https://github.com/privatenumber/minification-benchmarks
Compare the trophies indicating smallest size for Minified versus Minzipped (gzip). Generally the smallest minified size yields the smallest minified+gzip size, but there are some notable anomolies outside the range of statistical noise. It is not practical for a javascript minifier to take a compression algorithm into account - it would blow up the minify timings exponentially.
-
Bun v0.6.0 โ Bun's new JavaScript bundler and minifier
It would be helpful to see how Bun's minifier compares to the others with popular libraries:
https://github.com/privatenumber/minification-benchmarks
-
JS Uglify/Minify Gems?
JavaScript
-
Overview of the next-gen frontend dev tools
There are many minifiers such as terser and uglify. But, because minifying also require to parse the JS, it is actually possible to use esbuild and SWC to minify the code. Here's a benchmark of the main minifiers.
-
Overworld 1.0 is Live
Here's a comparison showing the major players with comparable stats at first glance. https://github.com/privatenumber/minification-benchmarks
-
Is anyone using Google Closure Compiler? And why not?
https://esbuild.github.io/ https://github.com/privatenumber/minification-benchmarks
- Parcel v2
- I never need webpack or babel anymore
-
๐งข Stefan's Web Weekly #6
privatenumber/minification-benchmarks โ JS minification benchmarks: babel-minify, esbuild, terser, uglify-js
What are some alternatives?
swc - Rust-based platform for the Web
vite - Next generation frontend tooling. It's fast!
terser - ๐ JavaScript parser, mangler and compressor toolkit for ES6+
esbuild - An extremely fast bundler for the web
V8 - The official mirror of the V8 Git repository
cash - An absurdly small jQuery alternative for modern browsers.
mocha-esbuild - Run tests with mocha compiled by esbuild
zepto - Zepto.js is a minimalist JavaScript library for modern browsers, with a jQuery-compatible API
fjb - fast javascript bundler :package:
npm-groovy-lint - Lint, format and auto-fix your Groovy / Jenkinsfile / Gradle files using command line
source-map-explorer - Analyze and debug space usage through source maps