Fork me on GitHub

Looking into a little; it looks like it is trivial to recover most of the functionality by continuing to work with Closure Library private API (and while retaining compatibility with the older private API), but some of the corner cases will be a little more difficult to reach and will take more digging. If curious:


it works because we run a module resolver that is aware of the resolution context


Ok that starts to make sense, thanks for the tip, I guess I will find it in the module-deps.js script


Other question related to that, I wonder why the module-deps.js is launched with node --eval? Why don't we pass cli parameters?


@richiardiandrea I don't understand the second question, but: module-deps.js file doesn't necessarily exist in filesystem so eval is easy way to run the code without first writing it to some file


oh got it, yeah so it is run from an in-memory string that is why


Usually the original file is inside jar and node wouldn't know about those


I though it was saved to disk first in some temp folder