On 2014/10/17 19:49, David Coppa wrote: > On Fri, Oct 17, 2014 at 7:46 PM, David Coppa <[email protected]> wrote: > > On Fri, Oct 17, 2014 at 5:34 PM, Stuart Henderson <[email protected]> wrote: > >> On 2014/10/15 02:54, Stuart Henderson wrote: > >>> Does this (log below) ring any bells? > >> > >> I didn't hit this on the next build. > >> > >>> lang/coffeescript - "npm ERR! Error: getaddrinfo EIO" > >> > >> coffeescript won't build unless it can make an https connection to > >> registry.npmjs.org, I didn't fancy digging into npm and it's so far > >> resistant to my attempts to mitm for some reason (sits with a > >> spinning \|/| cursor) so I'm not sure what it's trying to fetch > >> from there. > > > > # mitmdump --app-host npmjs.org
Oh I looked at porting that but got stuck because it wanted new py-openssl which wanted py-cryptography which needed CFFI ... (sslsplit normally works but for some reason failed with this one). > > 127.0.0.1 GET https://registry.npmjs.org/mkdirp > > << 200 OK 21.08kB > > 127.0.0.1 GET https://registry.npmjs.org/mkdirp/-/mkdirp-0.3.5.tgz > > << 200 OK 4.06kB > > So we need a new port for: > > https://github.com/substack/node-mkdirp > > to be a dependency for coffeescript... Isn't it in the main node package?
