Aws-xray-sdk-node: Unhandled rejection ReferenceError: processAddress is not defined

Created on 12 Sep 2018  路  5Comments  路  Source: aws/aws-xray-sdk-node

We are experiencing an issue with node_modules/aws-xray-sdk-core/lib/daemon_config.js

stack trace:

Unhandled rejection ReferenceError: processAddress is not defined
    at Object.<anonymous> (C:\****\node_modules\aws-xray-sdk-core\lib/daemon_config.js:24:17)
    at Module._compile (module.js:652:30)
    at Module._compile (C:\****\node_modules\pirates\lib\index.js:83:24)
    at Module._extensions..js (module.js:663:10)
    at Object.newLoader [as .js] (C:\****\node_modules\pirates\lib\index.js:88:7)
    at Module.load (module.js:565:32)
    at tryModuleLoad (module.js:505:12)
    at Function.Module._load (module.js:497:3)

OS: win
node: 8.11

bug

All 5 comments

Hi, thank you for reporting this issue. Do you have a short code snippet to reproduce the problem? I cannot reproduce this on unit test or my own sample app. It might be a missing keyword var at https://github.com/aws/aws-xray-sdk-node/blob/master/packages/core/lib/daemon_config.js#L24 but we want to be sure that you are having the same issue so we can provide the right fix. Please let me know.

Unfortunately, I need a time to provide an example (I can do it if it's a blocker for us).
I confirm, adding var fixes the issue.

PS: The issue somehow relates to babel transformations we use.

I'm happy to hear this workaround works for you. We will fix this and roll it out soon.

Sorry for the confusion earlier. This is scheduled in the next release after v2.0.1.

This issue is fixed as part of v2.1.0 release.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

JeremieDoctrine picture JeremieDoctrine  路  7Comments

ivanmartos picture ivanmartos  路  6Comments

thomasmichaelwallace picture thomasmichaelwallace  路  5Comments

wilson-burea picture wilson-burea  路  4Comments

CodingVampyre picture CodingVampyre  路  4Comments