Node.js client engine specification seems too restrictive

[CommunityUser]

The Node.js client specifies Node.js version >= 0.8.0 and <= 0.10.32. In package.json:

"engines": {
"node": ">=0.8.0 <=0.10.32"
},

Current version of node is 0.10.33, and npm install fails. Also enginestrict flag is used, further restricting the compatibility of the library.

https://www.npmjs.org/doc/files/package.json.html#enginestrict

[Kyle_Furlong]

Hey bdjurkovic,

There are natively compiled components which depend on the exact version of Node.js that you are installing into. We typically roll out support for the latest versions each time we release a new version of our Node.js agent. We have workarounds to get the newest versions working that come out after we release a version of our agent. Please let me know if you'd like to implement one of these workflows in your deployment process. I would only suggest this if you are planning on always staying on the bleeding edge version of Node.

Best regards,

Kyle

[CommunityUser]

Hello, thanks for the feedback. Yes I think for development, at least, we would like to be able to work with later than supported Node version; if the workaroud isn't too complicated. Please let me know what the workflow is. Thanks!

[Kyle_Furlong]

The simplest workaround is to fake your npm user agent:

npm config get user-agent

<user agent output here>

npm config set user-agent <modified user agent here>

The modification is to make the version the latest possible support by the appd package.