closure-compiler
zepto
Our great sponsors
| closure-compiler | zepto | |
|---|---|---|
| 14 | 1 | |
| 7,247 | 15,001 | |
| 0.6% | - | |
| 9.6 | 0.0 | |
| 8 days ago | over 1 year ago | |
| Java | HTML | |
| Apache License 2.0 | GNU General Public License v3.0 or later |
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".
zepto
-
Show HN: Auto-generate vanilla JavaScript alternatives for jQuery methods
Vanilla JS refers to Javascript that uses native browser methods instead of relying on a library. This is just replacing jQuery with another library constructed on the fly.
I don't see the point and there are already minimal and modern alternatives with the jQuery API like zepto and cash.
1) https://github.com/fabiospampinato/cash 2) https://github.com/madrobby/zepto
What are some alternatives?
swc - Rust-based platform for the Web
cash - An absurdly small jQuery alternative for modern browsers.
terser - 🗜 JavaScript parser, mangler and compressor toolkit for ES6+
replace-jquery - Automatically finds jQuery methods from existing projects and generates vanilla js alternatives.
V8 - The official mirror of the V8 Git repository
jQuery - jQuery JavaScript Library
tiny-events.js - TinyEvents is a tiny event utility library for modern browsers(IE 11+). Supports jQuery-like syntax. Just 1 kb gzipped.
npm-groovy-lint - Lint, format and auto-fix your Groovy / Jenkinsfile / Gradle files using command line
awesome-js-tooling-not-in-js - A curated list of JavaScript tooling not written in JavaScript
node - Node.js JavaScript runtime ✨🐢🚀✨