Of course, the "packages" being managed are themselves the subject of some discussion:<p>* <a href="https://news.ycombinator.com/item?id=11348798" rel="nofollow">https://news.ycombinator.com/item?id=11348798</a><p>Given how some of them are turning out to be one-liners, or 11-liners, one wag has suggested that Twitter could be an alternative Node.js repository, and has demonstrated how one would go about using Twitter as an alternative repository of such packages, using leftpad as an example:<p>* <a href="https://gist.github.com/rauchg/5b032c2c2166e4e36713" rel="nofollow">https://gist.github.com/rauchg/5b032c2c2166e4e36713</a>
A few days ago there was some discussion about GX, a language-agnostic package manager built around <a href="https://ipfs.io/" rel="nofollow">https://ipfs.io/</a><p><a href="https://news.ycombinator.com/item?id=11347163" rel="nofollow">https://news.ycombinator.com/item?id=11347163</a>
<a href="https://news.ycombinator.com/item?id=11364190" rel="nofollow">https://news.ycombinator.com/item?id=11364190</a> preceded your question by 8 hours. (-:
A wrapper over something like this...<p><pre><code> git clone https://[repo]/[module].git node_modules/[module]
</code></pre>
...and ability to provide dependency resolution along with custom runscripts?<p>Yes, we can. Not a rocket science. How many paranoid freaks will <i>actually</i> switch to it - that is the question.