Closure Tools Published to nom

[Chad Killingsworth]

Closure tools are now officially published to npm. We plan to maintain the nom packages as official release points.

• google-closure-compiler
• google-closure-templates
• google-closure-library

Notes about versioning:

npm uses semver versioning. The compiler and templates projects use date versioning while closure library has historically not been versioned.

To reconcile these differences, the compiler and templates date version number will be used as the MAJOR version. PATCH version numbers will primarily be used for tweaks to the NPM package structure.

Example version: 20150315.0.0

While this doesn’t follow the true spirit of semantic versioning, it allows us to maintain parity with other distribution channels.

Closure-library is expected to be versioned to match the latest compiler release and updated on approximately the same release schedule as the compiler.

Chad Killingsworth

Closure Compiler Committer

[Richard Connamacher]

Very cool.

What's in the google-closure-compiler/contrib/nodejs directory?

I have some Node bindings and unit tests I wrote up for Closure Library and was preparing to publish to the (currently defunct) 'closure-compiler' module, so you can simply do require('closure-compiler') to access the goog.* namespace in Node. It also includes a Node wrapper module for depswriter.py. Would you be interested in me contributing those to the core google-closure-library module?

[Chad Killingsworth]

The google-closure-compiler/contrib/nodejs folder houses the externs used to compile nodejs scripts with Closure-compiler. It is maintained by the community through PRs to the Closure-compiler project.

The google-closure-library package is simply a publication of the https://github.com/google/closure-library respository. The only changes have been to the package.json file. 

As for the node-wrapper module for depswriter.py, It would be best to ask about that in the closure-library-discuss group. While changes like that sound like a good fit for the project to me, getting PRs reviewed and merged into Closure-library has been challenging recently. Hopefully that will be changing soon.

Chad

[Chad Killingsworth]

I just realized this was cross posted into both groups. Hopefully maintainers will respond to the closure-library version.

[Richard Connamacher]

One request for google-closure-library on NPM: could you make the Node bootstrap file (closure/goog/bootstrap/nodejs.js) its 'main' file in package.json instead of closure/goog/base.js? That way you could simply do:

require("google-closure-library")

...and start using goog.require() in Node right away.

[Chad Killingsworth]

Yes I can do that - I would have already if I had known that existed. Hopefully somone will start merging my PRs for the package.json soon.

Chad

[John Lenz]

Can you assign them to me?

--

---
You received this message because you are subscribed to the Google Groups "Closure Compiler Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to closure-compiler-d...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/closure-compiler-discuss/ca39e79a-fb8b-43fa-985d-232511a605f3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.