[NodeJS] Installing AppDynamics agent sub-dependencies NPM from another repository

[gabriel.saldanha]

Hi there,

I have a host which only has access to the npm default registry (i.e., it's not open to the Internet).

During the `npm install` I get error while fetching appdynamics sub-dependencies:

```

"dependencies": {

"appdynamics-jre": "http://packages.appdynamics.com/nodejs/4.3.8.0/appdynamics-jre.tgz",

"appdynamics-libagent": "http://packages.appdynamics.com/nodejs/4.3.8.0/appdynamics-libagent.tgz",

"appdynamics-native": "http://packages.appdynamics.com/nodejs/4.3.8.0/appdynamics-native.tgz",

"appdynamics-protobuf": "http://packages.appdynamics.com/nodejs/4.3.8.0/appdynamics-protobuf.tgz",

"appdynamics-proxy": "http://packages.appdynamics.com/nodejs/4.3.8.0/appdynamics-proxy.tgz",

"appdynamics-zmq": "http://packages.appdynamics.com/nodejs/4.3.8.0/appdynamics-zmq.tgz",

},

```

It clearly happens because they are told to be fetched from `packages.appdynamics.com` domain. Is there a way to tell the `appdynamics` lib to download its dependencies from another repository (for example, my own artifactory where I could manually upload those)?

Thanks in advance,

- Gabriel Saldanha (@gcrsaldanha)

[Kyle.Furlong · Accepted solution]

Hi Gabriel,

The best way to accomplish an offline install is to package up an archive of the package folders, then simply transport them from the node_modules folder on the build machine to the node_modules folder on your app server.

There's one tricky bit which is that the npm user-agent on the build machine needs to match the one on your target server. You can ensure this by using this pair of commands:

• npm config get user-agent
• npm config set user-agent

Please let me know if you have any issues with this workflow.

Regards,

Kyle

[gabriel.saldanha]

Thanks for the clear answer, Kyle.

I'll keep you posted if it works!

Cheers,

- Gabriel Saldanha (@gcrsaldanha)