closure-compiler VS npm-groovy-lint

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.

Closure Compiler follows the same line of thinking:

https://github.com/google/closure-compiler/wiki/FAQ#closure-...

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.

The @template tag is supported by Google Closure Compiler

i'm not sure you want them to write back https://github.com/google/closure-compiler/pull/3958

time to fork

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".

You can run https://github.com/nvuillam/npm-groovy-lint via Jenkins on your Jenkinsfiles. Use https://github.com/nvuillam/npm-groovy-lint/blob/master/lib/.groovylintrc-recommended-jenkinsfile.json as the basis for your linter config and you should be good to go.

I made major changes to npm-groovy-lint (v10.1.0 can now take files as arguments) and VsCode Groovy Lint (fixed a lot of bugs in v2.0.0 ^^)