a workaround is to check in these dependancies in to the projects, so your build systen don't have to fetch them via npm, to bring the build through.
Am Dienstag, 26. März 2013 00:46:35 UTC+1 schrieb Daniel Wabyick: > > We have a build environment where our build servers do not have external > SSH access for security reasons. We've got hit by the problem like in the > following pull request [0], where an NPM dependency does not specify both > the git+https protocol. > > [0] https://github.com/jsdoc3/jsdoc/pull/352/files > > Since this was a dependency of another project, we didn't really have an > easy way to make this fix, and have to wait until it gets fixed in an NPM > exposed repository. > > It seems like 'a good thing' if NPM either a) had a setting to allow git > to imply git+https, or b) just always tried https if the git:// protocol > failed. > > > I'm interested in doing the work and making a pull request, but wanted to > see if there was a downside to this approach that I'm missing. Personally, > I would choose b) to keep settings to a minimum. > > > -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
