hehe, leftovers of 200MiB. Yeah so what I'm doing now is just writing my own client: curl uri, parse semver, walk and unzip
-
-
Replying to @yoshuawuyts
Ugh. Coming your way soon: 1) lifecycle scripts 2) cycles 3) deduplication, esp. for front-end
1 reply 0 retweets 0 likes -
Replying to @kemitchell
OH DAMN YOU'RE RIGHT. But umm, I could use `npm rebuild` for that couldn't I ? :P
1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts @kemitchell
dedupe is def more of an issue. Damn haha
2 replies 0 retweets 0 likes -
Replying to @yoshuawuyts
All considered, you almost certainly really, really want an npm@3 tree. What's wrong with committing node_modules?
1 reply 0 retweets 0 likes -
Replying to @kemitchell
I don't like having big changelogs in git. Maybe if LFS lands, then sure
1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts
Could you get a tarball to your container somehow?
1 reply 0 retweets 0 likes -
Replying to @kemitchell
would have to be from my local machine, which is a mac. So npm rebuild after that. idk; it also doesn't work for contribs :/
1 reply 0 retweets 0 likes -
-
Replying to @kemitchell @yoshuawuyts
But seriously, if you're interested in this stuff, have a look at https://github.com/kemitchell/flat-dependency-follower.js …
1 reply 0 retweets 1 like
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.