bunyan and dtrace-provider error

[ysak-y]

I install this module using npm install -g ask-cli. After install it, I got this error when type ask.

{ Error: Cannot find module './build/Release/DTraceProviderBindings'
    at Function.Module._resolveFilename (module.js:555:15)
    at Function.Module._load (module.js:482:25)
    at Module.require (module.js:604:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/opt/brew/lib/node_modules/ask-cli/node_modules/dtrace-provider/dtrace-provider.js:18:23)
    at Module._compile (module.js:660:30)
    at Object.Module._extensions..js (module.js:671:10)
    at Module.load (module.js:573:32)
    at tryModuleLoad (module.js:513:12)
    at Function.Module._load (module.js:505:3)
    at Module.require (module.js:604:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/opt/brew/lib/node_modules/ask-cli/node_modules/bunyan/lib/bunyan.js:79:18)
    at Module._compile (module.js:660:30)
    at Object.Module._extensions..js (module.js:671:10)
    at Module.load (module.js:573:32) code: 'MODULE_NOT_FOUND' }

  Usage: ask [options] [command]

  Command Line Interface for Alexa Skill Management API


  Options:

    -v, --version  output the version number of ask-cli
    -h, --help     output usage information


  Commands:

    init [options]       initialize the ask-cli with your Amazon developer account credentials
    deploy [options]     deploy a skill to your developer account
    new [options]        create a new skill project on your computer
    clone [options]      clone an existing skill project on your computer
    simulate [options]   simulate a user using your skill
    lambda               list of AWS Lambda commands
    api                  list of Alexa Skill Management API commands
    help [cmd]           display help for [cmd]

npm -v
5.6.0

What's wrong?

[RonWang]

Hi @ysak-y ,
This issue is actually brought by our dependency bunyan, which has been discussed in trentm/node-bunyan#502. So for the short term solution please follow the thread in the discussion for a better exposure of the issue.
Longer term we will implement our own debug framework to avoid those issues (we are also facing trentm/node-bunyan#66 this issue...) from them.