The npm community forum has been discontinued.
To discuss usage of npm, visit the GitHub Support Community.
npm install fail behind aggressive proxy
What I Wanted to Do
What Happened Instead
It doesn’t work behind our aggressive company proxy because the archive contains an other archive, cb-never-called-1.0.1.tgz, which can’t be uncompressed, so our proxy considers the archive is not safe and refuses to download it.
Is this file never-called-1.0.1.tgz necessary ? Should not it be corrected ?
$ npm --versions <!-- paste output here --> $ node -p process.platform <!-- paste output here -->