awesome-js-tooling-not-in-js
A curated list of JavaScript tooling not written in JavaScript (by RobinCsl)
closure-compiler
A JavaScript checker and optimizer. (by google)
| awesome-js-tooling-not-in-js | closure-compiler | |
|---|---|---|
| 7 | 15 | |
| 749 | 7,254 | |
| - | 0.3% | |
| 1.1 | 9.6 | |
| 8 months ago | 8 days ago | |
| Java | ||
| - | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
awesome-js-tooling-not-in-js
Posts with mentions or reviews of awesome-js-tooling-not-in-js.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-11-10.
-
Bun – fast JavaScript and CSS bundler
For a list of similar JavaScript tools that are written in other languages:
https://github.com/RobinCsl/awesome-js-tooling-not-in-js/
- Awesome JS Tooling not in JS
- A curated list of JavaScript tooling not written in JavaScript
- JavaScript Tooling Not in JavaScript
closure-compiler
Posts with mentions or reviews of closure-compiler.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-05-04.
-
Figma's Journey to TypeScript
Well, the nice thing with Python types is that the _only_ difference to untyped Python is the type annotations. Last time I worked with TypeScript (two and a half years ago), it felt more like a different language _similar_ to JS. In my experience it was quite... viral. With MyPy I've genuinely seen just specific parts of a code base become typed and didn't notice any friction.
I wonder what would happen if that proposal for type comments in JS went through. Would TypeScript become just a type checker / optimizing compiler?
Google's Closure had an (IMHO) nicer approach (https://github.com/google/closure-compiler/wiki/Types-in-the...), but I don't get the impression it'll ever catch on outside Google.
-
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?
What are some alternatives?
When comparing awesome-js-tooling-not-in-js and closure-compiler you can also consider the following projects:
swc - Rust-based platform for the Web
bun-releases-for-updater
terser - 🗜 JavaScript parser, mangler and compressor toolkit for ES6+
npm-groovy-lint - Lint, format and auto-fix your Groovy / Jenkinsfile / Gradle files using command line
V8 - The official mirror of the V8 Git repository
node - Node.js JavaScript runtime ✨🐢🚀✨
cash - An absurdly small jQuery alternative for modern browsers.
pyright - Static Type Checker for Python
zepto - Zepto.js is a minimalist JavaScript library for modern browsers, with a jQuery-compatible API
awesome-js-tooling-not-in-js vs swc
closure-compiler vs swc
awesome-js-tooling-not-in-js vs bun-releases-for-updater
closure-compiler vs terser
awesome-js-tooling-not-in-js vs npm-groovy-lint
closure-compiler vs V8
awesome-js-tooling-not-in-js vs node
closure-compiler vs cash
awesome-js-tooling-not-in-js vs pyright
closure-compiler vs zepto
awesome-js-tooling-not-in-js vs V8
closure-compiler vs npm-groovy-lint