Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Vagrant Test Fails

See original GitHub issue

I didn’t try installing via NPM but followed instructions to test with vagrant. Got an error, also tried installing nodegit inside the vagrant vb, both before and after install nodegit I got the following error:

vagrant@vagrant-ubuntu-trusty-64:~/bootstrap$ git hours
module.js:338
    throw err;
          ^
Error: Cannot find module '../build/Debug/nodegit.node'
    at Function.Module._resolveFilename (module.js:336:15)
    at Function.Module._load (module.js:278:25)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)
    at Object.<anonymous> (/usr/lib/node_modules/git-hours/node_modules/nodegit/dist/nodegit.js:18:12)
    at Module._compile (module.js:460:26)
    at Object.Module._extensions..js (module.js:478:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)
    at Object.<anonymous> (/usr/lib/node_modules/git-hours/src/index.js:4:11)
    at Module._compile (module.js:460:26)
    at Object.Module._extensions..js (module.js:478:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)

Issue Analytics

State:
Created 7 years ago
Reactions:2
Comments:6 (1 by maintainers)

Top GitHub Comments

1reaction

PhilAltoncommented, Dec 27, 2017

Had the same problem, and have found a work around:

Install nodegit manually (run npm install -g nodegit [as an administrator / i.e. sudo or cmd with admin privileges])
Locate the node_modules root directory (should now include both nodegit and git-hours). Navigate into nodegit’s build folder and copy the release folder. Now navigate to the node_modules/git-hours folder, and then to git-hour’s node_modules folder (which will contain a nodegit folder). Replace the git-hours\node_modules\nodegit\build\Release folder with the Release folder from node_modules\nodegit\build\Release. Furthermore, copy the folder again to the same directory, but this time name it Debug, not Release.

3). Try running git hours again, from within your chosen git repo.

0reactions

kimmobrunfeldtcommented, Aug 15, 2021

Vagrant setup is now out of scope for this repo, updated the instructions.