NodeJs agent fails to instantiate in AWS Lambda in runtime Node v12.x

[mkosterOST]

Earlier today I attempted to run a StackImpact agent in an AWS Lambda environment, using the NodeJS 12.x runtime. AWS Lambda currently uses NodeJS 12.16.3, specifically (Running on linux-x64). My call to "agent.start(params)" failed, with the following error message: "Finding/loading of native addon failed."

After this, I updated my local version of NodeJS to the same node version (12.16.3), and was able to reproduce the issue on a windows machine.

It appears that the Agent is failing to resolve an addon because the file abi-map.json does not contain a mapping from NodeJS v12.16.3 to the proper precompiled addon version. The file contains v12.16.0 and v12.16.1, but is missing subsequent minor versions of Node 12.

Modifying this file and adding v12.16.3 resolves the problem.

[jamaica474]

I'm seeing fallback as well. Can't install in aws-lambda(node 12) project

node --version v12.18.1

"yarn add stackimpact
yarn add v1.22.4
[1/4] Resolving packages...
warning stackimpact > node-gyp > request@2.88.2: request has been deprecated, see request/request#3142
[2/4] Fetching packages...
info fsevents@2.1.3: The platform "linux" is incompatible with this module.
info "fsevents@2.1.3" is an optional dependency and failed compatibility check. Excluding it from installation.
info fsevents@1.2.13: The platform "linux" is incompatible with this module.
info "fsevents@1.2.13" is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
warning "@jobtarget/sdk > promise-ftp@1.3.5" has unmet peer dependency "promise-ftp-common@^1.1.5".
[4/4] Building fresh packages...
[-/5] ⠐ waiting...
[5/5] ⠐ serverless
[-/5] ⠐ waiting...
[4/5] ⠐ stackimpact
error /home/jamaica/projects/distribution/node_modules/stackimpact: Command failed.
Exit code: 1
Command: node node-gyp-fallback.js
Arguments:
Directory: /home/jamaica/projects/distribution/node_modules/stackimpact
Output:
"