Aha! Conflicting info. Azure Functions seems to be the one to blame for reporting x86 to node-pre-gyp

[CbtSlave]

          Aha! Conflicting info. Azure Functions seems to be the one to blame for reporting x86 to node-pre-gyp

D:\home>node test.js
ia32 ia32

D:\home>node --version
v6.5.0

D:\home>cat test.js
console.log(process.arch, require("os").arch());

System info

System up time: 1.21:10:02
OS version: Microsoft Windows NT 6.2.9200.0
64 bit system: True
64 bit process: True

Environment variables

REMOTEDEBUGGINGBITVERSION = vx64
REMOTEDEBUGGINGPORT =
REMOTEDEBUGGINGVERSION = 11.0.611103.400
SCM_SKIP_SSL_VALIDATION = 0
SCM_USE_FUNCPACK = 0
ScmType = GitHub
SITE_BITNESS = AMD64

Originally posted by @DonKarlssonSan in #27 (comment)

[CbtSlave]

      Aha! Conflicting info. Azure Functions seems to be the one to blame for reporting x86 to node-pre-gyp

[CbtSlave]

D:\home>node test.js
ia32 ia32

D:\home>node --version
v6.5.0

D:\home>cat test.js
console.log(process.arch, require("os").arch());