Dependency resolution about closure-compiler-js HOT 5 CLOSED

Personally, I would love to ditch the Python for node tools.

On Sep 8, 2016 8:31 AM, "Philip Polkovnikov" [email protected]
wrote:

Is a translation of this folder
https://github.com/google/closure-library/tree/master/closure/bin/build
going to make its way into the project? I've made a translation
https://github.com/polkovnikov-ph/closure-test/blob/master/build/closure.js
back in 2014, but it was one of the first projects in JS, and it's horrible.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#19, or mute the
thread
https://github.com/notifications/unsubscribe-auth/ABMDKpbeSGUuEchzZoemvH9upKw3lrdXks5qoCpdgaJpZM4J4IVh
.

from closure-compiler-js.

I'm not 100% sure, nor have I seen that Python code before. I wonder if this is to do with the Closure dependency/module stuff.

@joeltine, looks like you were the last one to touch it?

from closure-compiler-js.

@samthor That code is used to solve goog.requires and pass files into compiler in correct order (i.e. as a toposort of a DAG). I've tried compiling with closure-compiler-js two files A and B (in this order) with A depending on B, and it didn't work for this reason.

from closure-compiler-js.

Echoing what @concavelenz said, I'd love to see those tools written in NodeJS. To be perfectly honest, it's probably low priority for the Closure Library team. I'd look at a PR if someone wanted to attempt adding them though.

from closure-compiler-js.

Dependency management for multiple systems is now supported in the main build: Please switch to the main distribution at https://github.com/google/closure-compiler-npm

from closure-compiler-js.