Bug: error reading config

[jasonkuhrt]

$ gh is
gh [error] Reading the config: Error: ENOENT, no such file or directory '/usr/local/Cellar/node/0.10.30/lib/node_modules'

$ gh -v                                                                                                                                                                                                                                                                master a1a71f9

fs.js:659
  return binding.readdir(pathModule._makeLong(path));
                 ^
Error: ENOENT, no such file or directory '/usr/local/Cellar/node/0.10.30/lib/node_modules'
    at Object.fs.readdirSync (fs.js:659:18)
    at Object.exports.getPlugins (/usr/local/lib/node_modules/gh/lib/base.js:250:18)
    at Help.run (/usr/local/lib/node_modules/gh/lib/cmds/help.js:57:20)
    at Object.<anonymous> (/usr/local/lib/node_modules/gh/bin/gh.js:53:16)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Function.Module.runMain (module.js:497:10)
    at startup (node.js:119:16)

[zenorocha]

Hey @jasonkuhrt, thanks for reporting!

Could you check if #289 fixes your problem?

[rands0n]

Hey man,

I want use this, but not working for me :(
I'll see what I can help!

[zenorocha]

Are you facing the exact same error log @randsonjs?

[rands0n]

Yes @zenorocha, the exact same error log!

[mrotaru]

+1, same problem

[rands0n]

Hey @mrotaru and @jasonkuhrt, try uninstall and re-install the node-gh. And erase or update the .gh.json file including ~/.gh.json.

That change worked for me. Also can work for you.

[henvic]

Old issue. Almost certainly fixed. And if not, we don't have the needed details anymore due to architectural changes.