How is the compiler supposed to be installed? #4003
-
|
Hello everyone! I discovered the Closure Library last year, and have been looking to try out the Closure Compiler out locally. From what I understood, I can download the JAR from Maven and use it with Java in the command-line, but the README in this repository tells otherwise – It says:
However, the NPM page says:
I am already aware of the fact that the JavaScript version of the Closure Compiler is no longer maintained, but in my past I've come across libraries on NPM that can be installed globally and are not actually made in JavaScript. Is the package currently published on NPM now a wrapper for the Java version? If not, should we edit the README to explicitly say that the NPM version is deprecated? Thank you! |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
When you install via NPM you should generally end up getting a version of the compiler that has been run through the Graal tool to turn it into a native binary. The NPM distribution of closure-compiler is handled by https://github.com/google/closure-compiler-npm You may want to create an issue over there if you have further questions. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you, Bradford. The NPM page listing says it is deprecated, which is why I had the question. |
Beta Was this translation helpful? Give feedback.
-
|
http://go/closure-compiler-npm-pr/268 will hopefully update the confusing message. |
Beta Was this translation helpful? Give feedback.
When you install via NPM you should generally end up getting a version of the compiler that has been run through the Graal tool to turn it into a native binary.
The NPM distribution of closure-compiler is handled by https://github.com/google/closure-compiler-npm
It is not deprecated.
You may want to create an issue over there if you have further questions.