xmldom dependency is a git repository about xml-crypto

[yaronn]

is this something that worked up until today (regression) or did you just
start to use the project today for the first time?

On Wed, Jan 8, 2014 at 1:18 PM, Peter Murray [email protected]:

We are having issues with the dependency in the package.json for xmldom
being a git repository reference. Which is then published in npm.

We are an enterprise and do not have a direct connection to the internet,
so when we use projects that then depend on this project, it cannot resolve
the xmldom, as we cannot connect to github from within our enterprise.

We do have an internal npm registry, so if your project actually
referenced the xmldom from npm itself, then this would work correctly.

Is it possible that you can release a version of this library using the
xmldom package from npm rather than the git repo reference?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/22
.

I'm on Twitter (@YaronNaveh http://twitter.com/#!/YaronNaveh)

[peter-murray]

First time using ws.js, that pulls in this project.

On 8 Jan 2014, at 11:25, "Yaron Naveh" <[email protected]mailto:[email protected]> wrote:

is this something that worked up until today (regression) or did you just
start to use the project today for the first time?

On Wed, Jan 8, 2014 at 1:18 PM, Peter Murray <[email protected]mailto:[email protected]>wrote:

We are having issues with the dependency in the package.json for xmldom
being a git repository reference. Which is then published in npm.

We are an enterprise and do not have a direct connection to the internet,
so when we use projects that then depend on this project, it cannot resolve
the xmldom, as we cannot connect to github from within our enterprise.

We do have an internal npm registry, so if your project actually
referenced the xmldom from npm itself, then this would work correctly.

Is it possible that you can release a version of this library using the
xmldom package from npm rather than the git repo reference?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/22
.

I'm on Twitter (@YaronNaveh http://twitter.com/#!/YaronNaveh)

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/22#issuecomment-31823731.

[yaronn]

ok I will see what I can do, give me a couple of days.
meanwhile I suggest you install ws.js on some machine outside the enterprise and check the module into your node_moduled library directly.

[yaronn]

please try installing xml-crypto again now, I have changed dependencies and it should work

[peter-murray]

It works as expected for this library, all served up from npm registry. Thanks for that and the fast turn around.

Sent from my iPad

On 8 Jan 2014, at 18:45, "Yaron Naveh" <[email protected]mailto:[email protected]> wrote:

please try installing xml-crypto again now, I have changed dependencies and it should work

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/22#issuecomment-31864503.